From: Matthew Wilcox <willy@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [linux-next:master 7193/9759] arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Fri, 6 May 2022 22:31:12 +0100 [thread overview]
Message-ID: <YnWToK1ocIWhpE59@casper.infradead.org> (raw)
In-Reply-To: <202205062129.oGoY3bdy-lkp@intel.com>
On Fri, May 06, 2022 at 09:59:14PM +0800, kernel test robot wrote:
> sparse warnings: (new ones prefixed by >>)
> >> arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const *addr @@ got void [noderef] __iomem * @@
> arch/sh/kernel/crash_dump.c:23:36: sparse: expected void const *addr
> arch/sh/kernel/crash_dump.c:23:36: sparse: got void [noderef] __iomem *
This code already produces a warning; the patch simply moves the warning
around. INVALID, WONTFIX, please stop reporting it.
next prev parent reply other threads:[~2022-05-06 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 13:59 [linux-next:master 7193/9759] arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2022-05-06 21:31 ` Matthew Wilcox [this message]
2022-05-07 1:28 ` Baoquan He
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=YnWToK1ocIWhpE59@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).