From: Thomas Richard <thomas.richard@bootlin.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
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 v7 00/10] Add pinctrl support for the AAEON UP board FPGA
Date: Tue, 10 Jun 2025 14:48:29 +0200 [thread overview]
Message-ID: <ddbaa399-6bad-4c97-8456-b597442e5be6@bootlin.com> (raw)
In-Reply-To: <CACRpkdZpn5xy+6yb-mQd6wDs05X0QqRCQo7QpL6=aEWtyU-zTg@mail.gmail.com>
On 6/10/25 14:42, Linus Walleij wrote:
> On Mon, Jun 9, 2025 at 11:51 AM Thomas Richard
> <thomas.richard@bootlin.com> wrote:
>
>> This is the seventh version of this series. Only few changes, the series has
>> been rebased on v6.16-rc1, the pinctrl patches were dropped as they were
>> already merged and a fix was added in upboard_pinctrl_dbg_show() to handle
>> the case upboard_pinctrl_pin_get_mode() returns an error.
>>
>> Best Regards,
>>
>> Thomas
>>
>> Signed-off-by: Thomas Richard <thomas.richard@bootlin.com>
>
> Looks good to me, some testbot was complaining about something
> but certainly we can merge the majority?
The export.h header file is missing in gpio-aggregator.
I can send a new version today. Or I can send a fix later.
What do you prefer ?
Regards,
Thomas
next prev parent reply other threads:[~2025-06-10 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 9:50 [PATCH v7 00/10] Add pinctrl support for the AAEON UP board FPGA Thomas Richard
2025-06-09 9:50 ` [PATCH v7 01/10] gpiolib: add support to register sparse pin range Thomas Richard
2025-06-09 9:51 ` [PATCH v7 02/10] gpio: aggregator: move GPIO forwarder allocation in a dedicated function Thomas Richard
2025-06-09 9:51 ` [PATCH v7 03/10] gpio: aggregator: refactor the code to add GPIO desc in the forwarder Thomas Richard
2025-06-09 9:51 ` [PATCH v7 04/10] gpio: aggregator: refactor the forwarder registration part Thomas Richard
2025-06-09 9:51 ` [PATCH v7 05/10] gpio: aggregator: update gpiochip_fwd_setup_delay_line() parameters Thomas Richard
2025-06-09 9:51 ` [PATCH v7 06/10] gpio: aggregator: export symbols of the GPIO forwarder library Thomas Richard
2025-06-09 15:20 ` kernel test robot
2025-06-09 9:51 ` [PATCH v7 07/10] gpio: aggregator: handle runtime registration of gpio_desc in gpiochip_fwd Thomas Richard
2025-06-09 9:51 ` [PATCH v7 08/10] gpio: aggregator: add possibility to attach data to the forwarder Thomas Richard
2025-06-09 9:51 ` [PATCH v7 09/10] lib/string_choices: Add str_input_output() helper Thomas Richard
2025-06-09 9:51 ` [PATCH v7 10/10] pinctrl: Add pin controller driver for AAEON UP boards Thomas Richard
2025-06-10 12:42 ` [PATCH v7 00/10] Add pinctrl support for the AAEON UP board FPGA Linus Walleij
2025-06-10 12:48 ` Thomas Richard [this message]
2025-06-10 22:10 ` Linus Walleij
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=ddbaa399-6bad-4c97-8456-b597442e5be6@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