From: Boris Brezillon <boris.brezillon@collabora.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the nand tree
Date: Fri, 20 Nov 2020 13:01:23 +0100 [thread overview]
Message-ID: <20201120130123.1ca9e7af@collabora.com> (raw)
In-Reply-To: <20201120122359.0bb7d98f@xps13>
On Fri, 20 Nov 2020 12:23:59 +0100
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hi Serge,
>
> Stephen Rothwell <sfr@canb.auug.org.au> wrote on Fri, 20 Nov 2020
> 11:39:29 +1100:
>
> > Hi all,
> >
> > After merging the nand tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/mtd/maps/physmap-bt1-rom.c: In function 'bt1_rom_map_read':
> > drivers/mtd/maps/physmap-bt1-rom.c:39:10: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> > 39 | shift = (unsigned int)src & 0x3;
> > | ^
> > drivers/mtd/maps/physmap-bt1-rom.c: In function 'bt1_rom_map_copy_from':
> > drivers/mtd/maps/physmap-bt1-rom.c:78:10: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> > 78 | shift = (unsigned int)src & 0x3;
> > | ^
> >
> > Introduced by commit
> >
> > 69a75a1a47d8 ("mtd: physmap: physmap-bt1-rom: Fix __iomem addrspace removal warning")
> >
>
> Too bad :/ I'll drop this patch for now, let's look for another
> solution...
uintptr_t cast?
next prev parent reply other threads:[~2020-11-20 12:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 0:39 linux-next: build warning after merge of the nand tree Stephen Rothwell
2020-11-20 11:23 ` Miquel Raynal
2020-11-20 12:01 ` Boris Brezillon [this message]
2020-11-20 12:58 ` Serge Semin
2020-11-20 13:01 ` Serge Semin
-- strict thread matches above, loose matches on Subject: below --
2023-12-01 1:56 Stephen Rothwell
2023-12-01 5:03 ` David Regan
2023-12-01 11:55 ` Miquel Raynal
2023-01-16 3:32 Stephen Rothwell
2022-02-08 6:00 Stephen Rothwell
2020-11-03 6:37 Stephen Rothwell
2020-11-06 4:31 ` Stephen Rothwell
2020-09-14 1:40 Stephen Rothwell
2020-03-11 2:06 Stephen Rothwell
2019-04-02 23:22 Stephen Rothwell
2019-04-03 7:49 ` Miquel Raynal
2018-10-08 0:38 Stephen Rothwell
2018-10-08 7:53 ` Miquel Raynal
2018-10-08 11:06 ` Stephen Rothwell
2018-07-19 2:28 Stephen Rothwell
2018-07-09 1:51 Stephen Rothwell
2018-07-09 6:16 ` Boris Brezillon
2018-07-09 6:51 ` Miquel Raynal
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=20201120130123.1ca9e7af@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=sfr@canb.auug.org.au \
/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).