From: Richard Weinberger <richard@sigma-star.at>
To: Richard Weinberger <richard@nod.at>,
linux-remoteproc@vger.kernel.org, upstream@sigma-star.at
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
mathieu.poirier@linaro.org, andersson@kernel.org,
upstream+rproc@sigma-star.at, Richard Weinberger <richard@nod.at>,
ohad@wizery.com, s-anna@ti.com, t-kristo@ti.com,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] rpmsg_ns: Work around TI non-standard message
Date: Mon, 14 Oct 2024 11:24:33 +0200 [thread overview]
Message-ID: <2480985.jE0xQCEvom@somecomputer> (raw)
In-Reply-To: <202410122348.irTWFe4S-lkp@intel.com>
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
next prev parent reply other threads:[~2024-10-14 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 12:39 [PATCH] rpmsg_ns: Work around TI non-standard message Richard Weinberger
2024-10-12 15:53 ` kernel test robot
2024-10-14 9:24 ` Richard Weinberger [this message]
2024-10-15 16:48 ` Mathieu Poirier
2024-10-15 16:58 ` Richard Weinberger
2024-10-15 17:56 ` Mathieu Poirier
2024-10-15 18:00 ` Richard Weinberger
2024-10-29 16:15 ` Romain Naour
2024-12-03 15:19 ` Andrew Davis
2024-12-03 16:40 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2480985.jE0xQCEvom@somecomputer \
--to=richard@sigma-star.at \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mathieu.poirier@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ohad@wizery.com \
--cc=richard@nod.at \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=upstream+rproc@sigma-star.at \
--cc=upstream@sigma-star.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.