[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2480985.jE0xQCEvom@somecomputer>
Date: Mon, 14 Oct 2024 11:24:33 +0200
From: Richard Weinberger <richard@...ma-star.at>
To: Richard Weinberger <richard@....at>, linux-remoteproc@...r.kernel.org, upstream@...ma-star.at
Cc: oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org, mathieu.poirier@...aro.org, andersson@...nel.org, upstream+rproc@...ma-star.at, Richard Weinberger <richard@....at>, ohad@...ery.com, s-anna@...com, t-kristo@...com, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] rpmsg_ns: Work around TI non-standard message
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 @@ got unsigned int [usertype] addr @@
> drivers/rpmsg/rpmsg_ns.c:55:25: sparse: expected restricted __rpmsg32 [assigned] [usertype] ns_addr
> drivers/rpmsg/rpmsg_ns.c:55:25: sparse: got unsigned int [usertype] addr
> >> drivers/rpmsg/rpmsg_ns.c:56:26: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __rpmsg32 [assigned] [usertype] ns_flags @@ got unsigned int [usertype] flags @@
> drivers/rpmsg/rpmsg_ns.c:56:26: sparse: expected restricted __rpmsg32 [assigned] [usertype] ns_flags
> drivers/rpmsg/rpmsg_ns.c:56:26: sparse: got unsigned int [usertype] flags
sprase is right.
I missed to replace u32 in the struct by __rpmsg32.
Thanks,
//richard
--
sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y
Powered by blists - more mailing lists