From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Enrico Weigelt <info@metux.net>
Subject: Re: linux-next: build warning after merge of the gpio tree
Date: Thu, 27 Jun 2019 15:57:46 +0100 [thread overview]
Message-ID: <CACRpkda1EgeRqgRZgNn+F7RSHonPE=s8c15uiKYtzg8NOWqvYw@mail.gmail.com> (raw)
In-Reply-To: <20190627181941.1222cb9c@canb.auug.org.au>
On Thu, Jun 27, 2019 at 9:20 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> After merging the gpio tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/gpio/gpio-amd-fch.c: In function 'amd_fch_gpio_probe':
> drivers/gpio/gpio-amd-fch.c:171:49: warning: passing argument 2 of 'devm_ioremap_resource' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
> priv->base = devm_ioremap_resource(&pdev->dev, &amd_fch_gpio_iores);
> ^~~~~~~~~~~~~~~~~~~
> In file included from include/linux/platform_device.h:13,
> from drivers/gpio/gpio-amd-fch.c:15:
> include/linux/device.h:708:15: note: expected 'struct resource *' but argument is of type 'const struct resource *'
> void __iomem *devm_ioremap_resource(struct device *dev, struct resource *res);
> ^~~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> 9bb2e0452508 ("gpio: amd: Make resource struct const")
OK I dropped this commit until Enrico get some time to figure out
what's going wrong here.
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-06-27 14:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 8:19 linux-next: build warning after merge of the gpio tree Stephen Rothwell
2019-06-27 14:57 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 8:36 Stephen Rothwell
2020-01-09 4:16 Stephen Rothwell
2019-11-05 6:43 Stephen Rothwell
2019-11-07 8:35 ` Linus Walleij
2019-02-25 4:52 Stephen Rothwell
2018-12-18 5:41 Stephen Rothwell
2018-11-06 1:15 Stephen Rothwell
2018-11-06 7:24 ` Uwe Kleine-König
2018-01-11 4:06 Stephen Rothwell
2018-01-11 9:19 ` Linus Walleij
2017-05-30 3:52 Stephen Rothwell
2016-11-14 5:31 Stephen Rothwell
2016-09-13 3:18 Stephen Rothwell
2016-06-16 4:32 Stephen Rothwell
2016-06-16 10:02 ` Linus Walleij
2014-03-07 3:59 Stephen Rothwell
2014-03-07 6:16 ` Linus Walleij
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='CACRpkda1EgeRqgRZgNn+F7RSHonPE=s8c15uiKYtzg8NOWqvYw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).