From: Mark Brown <broonie@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
bui duc phuc <phucduc.bui@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the gpio-brgl tree
Date: Wed, 2 Sep 2026 12:49:52 +0100 [thread overview]
Message-ID: <apgNYDiSiPmNZspF@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
Hi all,
After merging the gpio-brgl tree, today's linux-next build
(arm64 defconfig) failed like this:
/tmp/next/build/drivers/gpio/gpio-altera.c: In function 'altera_gpio_probe':
/tmp/next/build/drivers/gpio/gpio-altera.c:224:21: error: 'irq' undeclared (first use in this function); did you mean 'girq'?
224 | if (irq != -ENXIO)
| ^~~
| girq
Caused by commit
6e6e585b603e4 (gpio: altera: Handle errors from optional IRQ lookup)
I have used the tree from 20260901 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-09-02 11:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 11:49 Mark Brown [this message]
2026-09-02 12:36 ` linux-next: build failure after merge of the gpio-brgl tree Bui Duc Phuc
2026-09-03 4:14 ` Bui Duc Phuc
-- 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-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=apgNYDiSiPmNZspF@sirena.org.uk \
--to=broonie@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=phucduc.bui@gmail.com \
/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