From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>,
"Kefeng Wang" <wangkefeng.wang@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Will Deacon" <will@kernel.org>, "Christoph Hellwig" <hch@lst.de>,
"Russell King" <rmk+kernel@armlinux.org.uk>
Subject: Re: drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Wed, 09 Nov 2022 08:33:30 +0100 [thread overview]
Message-ID: <5f51b4bd-3bc2-487b-aacd-9d0a1129c615@app.fastmail.com> (raw)
In-Reply-To: <202211091154.quYhgunB-lkp@intel.com>
On Wed, Nov 9, 2022, at 04:54, kernel test robot wrote:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: f141df371335645ce29a87d9683a3f79fba7fd67
> commit: d803336abdbc1bfacdb32b2cf9f4fdbee072b8ee ARM: mm: kill unused
> runtime hook arch_iounmap()
Thanks for the report, but I think it might be better to stop
reporting address space violations from this patch, because it
only started showing existing known issues with a slightly
different error message, or flagging issues on arm32 that
were previously shown on other architectures.
> sparse warnings: (new ones prefixed by >>)
> drivers/remoteproc/st_remoteproc.c:98:12: sparse: sparse: incorrect
> type in assignment (different address spaces) @@ expected void *va
> @@ got void [noderef] __iomem * @@
> drivers/remoteproc/st_remoteproc.c:98:12: sparse: expected void
> *va
> drivers/remoteproc/st_remoteproc.c:98:12: sparse: got void
> [noderef] __iomem *
>>> drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *io_addr @@ got void *va @@
Arnd
next prev parent reply other threads:[~2022-11-09 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 3:54 kernel test robot
2022-11-09 7:33 ` Arnd Bergmann [this message]
2022-11-09 7:57 ` Chen, Rong A
-- strict thread matches above, loose matches on Subject: below --
2022-08-06 4:54 kernel test robot
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=5f51b4bd-3bc2-487b-aacd-9d0a1129c615@app.fastmail.com \
--to=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®