From: "Arnd Bergmann" <arnd@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: linux-sunxi@lists.linux.dev,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Vladimir Oltean" <olteanv@gmail.com>,
"Vinod Koul" <vkoul@kernel.org>,
linux-phy@lists.infradead.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 13/13] gpiolib: remove linux/gpio.h
Date: Tue, 30 Jun 2026 15:31:45 +0200 [thread overview]
Message-ID: <6114033d-ff33-4551-8af1-c82bae0e03bf@app.fastmail.com> (raw)
In-Reply-To: <20260630132838.113F91F00A3A@smtp.kernel.org>
On Tue, Jun 30, 2026, at 15:28, sashiko-bot@kernel.org wrote:
>> - When this work is complete (will require some of the items in the
>> - following ongoing work as well) we can delete the old global
>> - numberspace accessors from <linux/gpio.h> and eventually delete
>> - <linux/gpio.h> altogether.
>> + following ongoing work as well) we can delete <linux/gpio/lagacy.h>.
> ^^^^^^^^
> [Severity: Low]
> This isn't a bug, but there is a typo here (lagacy.h instead of legacy.h).
Fixed now for v2.
>> -#ifdef CONFIG_GPIOLIB_LEGACY
>> -#include <linux/gpio/legacy.h>
>> -#endif /* CONFIG_GPIOLIB_LEGACY */
>> -
>> -#endif /* __LINUX_GPIO_H */
>
> [Severity: Low]
> Does removing this header break the build for remaining unconverted legacy
> GPIO consumers?
There are a few more patches in flight that all have to be applied
before this one.
Arnd
next prev parent reply other threads:[~2026-06-30 13:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 13:26 [PATCH 00/13] treewide: replace linux/gpio.h Arnd Bergmann
2026-06-29 13:26 ` [PATCH 01/13] ARM: replace linux/gpio.h inclusions Arnd Bergmann
2026-06-29 13:26 ` [PATCH 02/13] m68k/coldfire: " Arnd Bergmann
2026-06-29 13:26 ` [PATCH 03/13] mips: " Arnd Bergmann
2026-06-30 22:08 ` Philippe Mathieu-Daudé
2026-06-29 13:26 ` [PATCH 04/13] sh: " Arnd Bergmann
2026-06-30 22:08 ` Philippe Mathieu-Daudé
2026-06-29 13:26 ` [PATCH 05/13] mfd: " Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-29 13:26 ` [PATCH 06/13] [net-next] net: " Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-29 13:26 ` [PATCH 07/13] ASoC: " Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-29 13:26 ` [PATCH 08/13] pcmcia: " Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-30 13:36 ` Arnd Bergmann
2026-06-29 13:26 ` [PATCH 09/13] phy: " Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-30 13:37 ` Arnd Bergmann
2026-06-29 13:26 ` [PATCH 10/13] media: " Arnd Bergmann
2026-06-29 13:26 ` [PATCH 11/13] Input: matrix_keyboard - replace linux/gpio.h inclusion Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-29 13:26 ` [PATCH 12/13] gpib: gpio: " Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-29 13:26 ` [PATCH 13/13] gpiolib: remove linux/gpio.h Arnd Bergmann
2026-06-30 13:28 ` sashiko-bot
2026-06-30 13:31 ` Arnd Bergmann [this message]
2026-06-30 22:09 ` Philippe Mathieu-Daudé
2026-06-29 14:01 ` [PATCH 00/13] treewide: replace linux/gpio.h Andreas Schwab
2026-06-29 14:24 ` Arnd Bergmann
2026-06-30 7:53 ` Bartosz Golaszewski
2026-06-30 21:39 ` Linus Walleij
2026-07-01 0:00 ` patchwork-bot+netdevbpf
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=6114033d-ff33-4551-8af1-c82bae0e03bf@app.fastmail.com \
--to=arnd@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
/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