From: broonie@kernel•org
To: Bartosz Golaszewski <brgl@bgdev•pl>
Cc: Florian Fainelli <f.fainelli@gmail•com>,
Xiang wangx <wangxiang@cdjrlc•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
linux-gpio@vger•kernel.org
Subject: linux-next: build failure after merge of the gpio-brgl tree
Date: Mon, 13 Dec 2021 20:31:12 +0000 [thread overview]
Message-ID: <20211213203112.969238-1-broonie@kernel.org> (raw)
Hi all,
After merging the gpio-brgl tree, today's linux-next build (x86_64
allmodconfig) failed like this:
/tmp/next/build/drivers/gpio/gpio-bcm-kona.c:508:34: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier]
508 | static const struct of_device_id const bcm_kona_gpio_of_match[] = {
| ^~~~~
cc1: all warnings being treated as errors
Caused by commit
19784a059cf47b ("gpio: bcm-kona: add const to of_device_id")
I used the tree from yesterday instead.
next reply other threads:[~2021-12-13 20:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 20:31 broonie [this message]
2021-12-14 3:12 ` linux-next: build failure after merge of the gpio-brgl tree Florian Fainelli
2021-12-17 6:17 ` Stephen Rothwell
2021-12-17 9:14 ` Bartosz Golaszewski
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 7:18 Stephen Rothwell
2025-10-20 0:56 Stephen Rothwell
2025-10-20 1:27 ` Stephen Rothwell
2025-10-17 14:47 Mark Brown
2025-10-17 14:52 ` Bartosz Golaszewski
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-20 5:51 Stephen Rothwell
2021-12-20 12:46 ` Andy Shevchenko
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=20211213203112.969238-1-broonie@kernel.org \
--to=broonie@kernel$(echo .)org \
--cc=brgl@bgdev$(echo .)pl \
--cc=f.fainelli@gmail$(echo .)com \
--cc=linux-gpio@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=wangxiang@cdjrlc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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