From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the gpio-brgl tree
Date: Mon, 20 Dec 2021 14:46:01 +0200 [thread overview]
Message-ID: <CAHp75Vd0xWe8HeNp=+njJQhFqSGF-74KdZ+oXMTzmGRFQ9arzg@mail.gmail.com> (raw)
In-Reply-To: <20211220165103.0d75d56d@canb.auug.org.au>
On Mon, Dec 20, 2021 at 11:22 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the gpio-brgl tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpio/gpio-rda.c: In function 'rda_gpio_probe':
> drivers/gpio/gpio-rda.c:200:22: error: unused variable 'np' [-Werror=unused-variable]
> 200 | struct device_node *np = pdev->dev.of_node;
> | ^~
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> 448cf90513d9 ("gpio: Get rid of duplicate of_node assignment in the drivers")
>
> I have used the gpio-brgl tree from next-20211217 (with the revert) for today.
My fault, sorry. Fix patch is on the way!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-12-20 12:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 5:51 linux-next: build failure after merge of the gpio-brgl tree Stephen Rothwell
2021-12-20 12:46 ` Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 3:33 Stephen Rothwell
2024-02-23 7:51 ` Bartosz Golaszewski
2024-02-23 12:29 ` Andy Shevchenko
2024-02-25 1:58 ` Stephen Rothwell
2024-02-26 19:07 ` Bartosz Golaszewski
2023-10-13 4:14 Stephen Rothwell
2023-10-13 6:44 ` Bartosz Golaszewski
2023-03-23 1:29 Stephen Rothwell
2023-03-22 19:50 ` William Breathitt Gray
2023-03-23 13:32 ` Bartosz Golaszewski
2021-12-13 20:31 broonie
2021-12-14 3:12 ` Florian Fainelli
2021-12-17 6:17 ` Stephen Rothwell
2021-12-17 9:14 ` Bartosz Golaszewski
2021-11-15 23:51 Stephen Rothwell
2021-11-17 21:29 ` Rob Herring
2021-11-18 0:29 ` Stephen Rothwell
2021-11-23 2:04 ` Stephen Rothwell
2021-12-02 3:16 ` Stephen Rothwell
2021-02-18 6:54 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='CAHp75Vd0xWe8HeNp=+njJQhFqSGF-74KdZ+oXMTzmGRFQ9arzg@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.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).