From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: kernel test robot <lkp@intel.com>, <kbuild-all@lists.01.org>,
<linux-kernel@vger.kernel.org>, <linux-mtd@lists.infradead.org>
Subject: Re: drivers/mtd/maps/physmap-bt1-rom.c:78:18: sparse: sparse: cast removes address space '__iomem' of expression
Date: Tue, 10 Nov 2020 16:35:56 +0100 [thread overview]
Message-ID: <20201110163556.3e3423f6@xps13> (raw)
In-Reply-To: <20201110113827.hl5i27cpl6exo3md@mobilestation>
Hi Serge,
Serge Semin <Sergey.Semin@baikalelectronics.ru> wrote on Tue, 10 Nov
2020 14:38:27 +0300:
> Hello Miquel,
>
> A situation noted by the warning below won't cause any problem because
> the casting is done to a non-dereferenced variable. It is utilized
> as a pointer bias later in that function. Shall we just ignore the
> warning or still fix it somehow?
Do you think the cast to a !__iomem value is mandatory here?
Perhaps if you find an elegant wait to avoid the warning it would be
nice, otherwise I guess we'll let it aside as a false positive.
Cheers,
Miquèl
next prev parent reply other threads:[~2020-11-10 15:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 4:42 drivers/mtd/maps/physmap-bt1-rom.c:78:18: sparse: sparse: cast removes address space '__iomem' of expression kernel test robot
2020-11-10 11:38 ` Serge Semin
2020-11-10 15:35 ` Miquel Raynal [this message]
2020-11-11 19:22 ` Serge Semin
2020-11-12 8:27 ` Miquel Raynal
2020-11-12 11:20 ` Serge Semin
2020-11-12 15:00 ` Vignesh Raghavendra
2020-11-12 15:27 ` Serge Semin
2020-11-12 15:43 ` Miquel Raynal
2020-11-12 16:10 ` Serge Semin
2020-11-12 16:15 ` Miquel Raynal
2020-11-12 16:21 ` Serge Semin
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=20201110163556.3e3423f6@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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).