From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-gpio@vger.kernel.org, kernel@pengutronix.de
Subject: Re: linux-next: build warning after merge of the gpio tree
Date: Tue, 6 Nov 2018 08:24:30 +0100 [thread overview]
Message-ID: <20181106072430.vub6xjvyof2agj3h@pengutronix.de> (raw)
In-Reply-To: <20181106121502.00efbd07@canb.auug.org.au>
Hi Linus,
On Tue, Nov 06, 2018 at 12:15:02PM +1100, Stephen Rothwell wrote:
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpio/gpiolib.c:1514:12: warning: 'devm_gpio_chip_match' defined but not used [-Wunused-function]
> static int devm_gpio_chip_match(struct device *dev, void *res, void *data)
> ^~~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> 48207d7595d2 ("gpio: drop devm_gpiochip_remove()")
I noticed this, too, but didn't tell immediately because I thought I'd
have to resent this patch and then forgot as you applied yourself.
Sorry for that, the obvious resolution is to drop
devm_gpio_chip_match(). Feel free to squash that into 48207d7595d2. If
your branch is already stable I can provide a patch for that.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2018-11-06 7:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 1:15 linux-next: build warning after merge of the gpio tree Stephen Rothwell
2018-11-06 7:24 ` Uwe Kleine-König [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-06-27 8:19 Stephen Rothwell
2019-06-27 14:57 ` Linus Walleij
2019-02-25 4:52 Stephen Rothwell
2018-12-18 5:41 Stephen Rothwell
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=20181106072430.vub6xjvyof2agj3h@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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).