Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-12-03 Thread Andrew Davis
On 10/15/24 1:00 PM, Richard Weinberger wrote: Am Dienstag, 15. Oktober 2024, 19:56:08 CEST schrieb Mathieu Poirier: In my opinion the real fix here is to get TI to use the standard message announcement structure. The ->desc field doesn't seem to be that useful since it gets discarted. This i

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-12-03 Thread Richard Weinberger
Andrew, Am Dienstag, 3. Dezember 2024, 16:19:31 CET schrieb Andrew Davis: > On 10/15/24 1:00 PM, Richard Weinberger wrote: > > Am Dienstag, 15. Oktober 2024, 19:56:08 CEST schrieb Mathieu Poirier: > In my opinion the real fix here is to get TI to use the standard message > announcement s

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-10-29 Thread Romain Naour
Hello Richard, All, Le 15/10/2024 à 20:00, Richard Weinberger a écrit : > Am Dienstag, 15. Oktober 2024, 19:56:08 CEST schrieb Mathieu Poirier: In my opinion the real fix here is to get TI to use the standard message announcement structure. The ->desc field doesn't seem to be that usefu

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-10-15 Thread Richard Weinberger
Am Dienstag, 15. Oktober 2024, 19:56:08 CEST schrieb Mathieu Poirier: > > > In my opinion the real fix here is to get TI to use the standard message > > > announcement structure. The ->desc field doesn't seem to be that useful > > > since > > > it gets discarted. > > > > This is for the future,

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-10-15 Thread Mathieu Poirier
On Tue, Oct 15, 2024 at 06:58:33PM +0200, Richard Weinberger wrote: > Mathieu, > > Am Dienstag, 15. Oktober 2024, 18:48:08 CEST schrieb Mathieu Poirier: > > Good morning Richard, > > > > On Fri, Oct 11, 2024 at 02:39:22PM +0200, Richard Weinberger wrote: > > > Texas Instruments ships a patch in t

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-10-15 Thread Richard Weinberger
Mathieu, Am Dienstag, 15. Oktober 2024, 18:48:08 CEST schrieb Mathieu Poirier: > Good morning Richard, > > On Fri, Oct 11, 2024 at 02:39:22PM +0200, Richard Weinberger wrote: > > Texas Instruments ships a patch in their vendor kernels, > > which adds a new NS message that includes a description f

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-10-15 Thread Mathieu Poirier
Good morning Richard, On Fri, Oct 11, 2024 at 02:39:22PM +0200, Richard Weinberger wrote: > Texas Instruments ships a patch in their vendor kernels, > which adds a new NS message that includes a description field. > While TI is free to do whatever they want in their copy of the kernel, > it become

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-10-14 Thread Richard Weinberger
Am Samstag, 12. Oktober 2024, 17:53:16 CEST schrieb kernel test robot: > sparse warnings: (new ones prefixed by >>) > >> drivers/rpmsg/rpmsg_ns.c:55:25: sparse: sparse: incorrect type in > >> assignment (different base types) @@ expected restricted __rpmsg32 > >> [assigned] [usertype] ns_addr

Re: [PATCH] rpmsg_ns: Work around TI non-standard message

2024-10-12 Thread kernel test robot
Hi Richard, kernel test robot noticed the following build warnings: [auto build test WARNING on remoteproc/rpmsg-next] [also build test WARNING on linus/master v6.12-rc2 next-20241011] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to