From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Walleij" <linusw@kernel.org>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Mehmet Fide" <mehmet.fide@screeningeagle.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>,
"Dan Carpenter" <error27@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: fix CONFIG_PINCTRL=n build failure
Date: Fri, 25 Sep 2026 20:06:15 +0200 [thread overview]
Message-ID: <1dd2a465-44ae-4bb0-9cfd-1e06cef5ac9c@app.fastmail.com> (raw)
In-Reply-To: <CAD++jLmteSSyzEbfv=mnxBCehZOoDtshskvAhrrVWMXjcFWM=g@mail.gmail.com>
On Fri, Sep 25, 2026, at 18:14, Linus Walleij wrote:
> On Fri, Sep 25, 2026 at 3:00 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> If pinctrl/consumer.h is included before linux/errno.h, the missing
>> error number macros cause a build failure:
>>
>> In file included from drivers/gpu/drm/tilcdc/tilcdc_drv.c:9:
>> include/linux/pinctrl/consumer.h:110:10: error: use of undeclared identifier 'ENOTSUPP'
>> 110 | return -ENOTSUPP;
>> | ^~~~~~~~
>>
>> Include linux/errno.h indirectly.
>>
>> Fixes: b44aec87658e ("pinctrl: make the CONFIG_PINCTRL=n gpio config stubs return -ENOTSUPP")
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> I think this is already fixed by:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/commit/?id=c2d996d9c6dab31ae41d19507c2b7ef8dbc14602
Right, I was still on yesterday's linux-next, so I did not see that.
Arnd
prev parent reply other threads:[~2026-09-25 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 12:59 Arnd Bergmann
2026-09-25 16:14 ` Linus Walleij
2026-09-25 18:06 ` Arnd Bergmann [this message]
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=1dd2a465-44ae-4bb0-9cfd-1e06cef5ac9c@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=error27@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mehmet.fide@screeningeagle.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
all inboxes | Powered by JetHome®