From: Thomas Richard <thomas.richard@bootlin.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kees Cook <kees@kernel.org>, Andy Shevchenko <andy@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, DanieleCleri@aaeon.eu,
GaryWang@aaeon.com.tw, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v8 00/10] Add pinctrl support for the AAEON UP board FPGA
Date: Tue, 15 Jul 2025 15:13:32 +0200 [thread overview]
Message-ID: <824ec6d1-4272-44c7-b3bb-93d716ed3d43@bootlin.com> (raw)
In-Reply-To: <CAMRc=MfS5Em65n0fwbu8JtJsc3rTgQO5cv+PymSonJtf6_zRKQ@mail.gmail.com>
On 6/25/25 10:26 AM, Bartosz Golaszewski wrote:
> On Wed, Jun 11, 2025 at 11:00 AM Thomas Richard
> <thomas.richard@bootlin.com> wrote:
>>
>> This is the eighth version of this series. I just added a missing header
>> file in gpio-aggregator driver to fix a build warning reported by a kernel
>> test robot [1].
>>
>> [1] https://lore.kernel.org/oe-kbuild-all/202506092324.XqSwWl1z-lkp@intel.com/
>>
>> Best Regards,
>>
>> Thomas
>>
>> Signed-off-by: Thomas Richard <thomas.richard@bootlin.com>
>> ---
>
> This series looks pretty good now, any objections to picking it up? As
> usual - I can take the GPIO patches and provide an immutable branch
> for Linus to pull.
Hi Bartosz,
When do you plan to pick the patches? Will it be ok for next merge window?
Best Regards,
Thomas
next prev parent reply other threads:[~2025-07-15 13:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 9:00 Thomas Richard
2025-06-11 9:00 ` [PATCH v8 01/10] gpiolib: add support to register sparse pin range Thomas Richard
2025-06-11 9:00 ` [PATCH v8 02/10] gpio: aggregator: move GPIO forwarder allocation in a dedicated function Thomas Richard
2025-06-11 9:00 ` [PATCH v8 03/10] gpio: aggregator: refactor the code to add GPIO desc in the forwarder Thomas Richard
2025-06-11 9:00 ` [PATCH v8 04/10] gpio: aggregator: refactor the forwarder registration part Thomas Richard
2025-06-11 9:00 ` [PATCH v8 05/10] gpio: aggregator: update gpiochip_fwd_setup_delay_line() parameters Thomas Richard
2025-06-11 9:00 ` [PATCH v8 06/10] gpio: aggregator: export symbols of the GPIO forwarder library Thomas Richard
2025-06-11 9:00 ` [PATCH v8 07/10] gpio: aggregator: handle runtime registration of gpio_desc in gpiochip_fwd Thomas Richard
2025-06-11 9:00 ` [PATCH v8 08/10] gpio: aggregator: add possibility to attach data to the forwarder Thomas Richard
2025-06-11 9:00 ` [PATCH v8 09/10] lib/string_choices: Add str_input_output() helper Thomas Richard
2025-06-11 9:00 ` [PATCH v8 10/10] pinctrl: Add pin controller driver for AAEON UP boards Thomas Richard
2025-06-25 8:26 ` [PATCH v8 00/10] Add pinctrl support for the AAEON UP board FPGA Bartosz Golaszewski
2025-07-15 13:13 ` Thomas Richard [this message]
2025-07-15 13:17 ` Bartosz Golaszewski
2025-07-23 8:43 ` Bartosz Golaszewski
2025-07-26 14:17 ` Linus Walleij
2025-07-29 8:03 ` Bartosz Golaszewski
2025-08-11 9:25 ` Bartosz Golaszewski
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=824ec6d1-4272-44c7-b3bb-93d716ed3d43@bootlin.com \
--to=thomas.richard@bootlin.com \
--cc=DanieleCleri@aaeon.eu \
--cc=GaryWang@aaeon.com.tw \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--cc=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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®