From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Jonas Gorski" <jonas.gorski@gmail.com>,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
"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 pinctrl tree
Date: Tue, 30 Mar 2021 09:51:41 +0200 [thread overview]
Message-ID: <CACRpkdZbtr3igRpzfpujH3WA3Es6JGu7GxTFTCSKX9f-3uYOpw@mail.gmail.com> (raw)
In-Reply-To: <20210330170744.6a1519b0@canb.auug.org.au>
On Tue, Mar 30, 2021 at 8:07 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> After merging the pinctrl tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/pinctrl/bcm/pinctrl-bcm6362.c: In function 'bcm6362_set_gpio':
> drivers/pinctrl/bcm/pinctrl-bcm6362.c:503:8: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> 503 | (uint32_t) desc->drv_data, 0);
> | ^
>
> Introduced by commit
>
> 705791e23ecd ("pinctrl: add a pincontrol driver for BCM6362")
Ha! The 0day robot didn't see it. Good that we have so many layers.
I bet Álvaro will have a patch to fix it in no time.
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-03-30 7:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 6:07 linux-next: build warning after merge of the pinctrl tree Stephen Rothwell
2021-03-30 7:51 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-21 7:11 Stephen Rothwell
2022-04-21 14:12 ` Linus Walleij
2022-04-21 18:05 ` Stefan Wahren
2021-10-27 11:01 Stephen Rothwell
2021-10-27 11:10 ` Marc Zyngier
2021-10-28 7:03 ` Mauro Carvalho Chehab
2022-01-20 3:25 ` Stephen Rothwell
2022-03-18 7:31 ` Stephen Rothwell
2022-06-05 23:33 ` Stephen Rothwell
2020-04-17 2:27 Stephen Rothwell
2020-04-17 10:23 ` Linus Walleij
2018-10-11 3:17 Stephen Rothwell
2018-10-11 7:51 ` Linus Walleij
2017-06-30 4:56 Stephen Rothwell
2017-06-30 4:57 ` Stephen Rothwell
2017-06-30 6:59 ` Geert Uytterhoeven
2017-06-30 13:48 ` Linus Walleij
2017-01-03 4:37 Stephen Rothwell
2015-05-20 6:40 Stephen Rothwell
2015-05-20 7:14 ` Linus Walleij
2014-05-19 6:59 Stephen Rothwell
2014-05-19 9:03 ` Maxime Ripard
2013-12-13 4:06 Stephen Rothwell
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=CACRpkdZbtr3igRpzfpujH3WA3Es6JGu7GxTFTCSKX9f-3uYOpw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=noltari@gmail.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).