From: Linus Walleij <linus.walleij@linaro.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Thomas Richard <thomas.richard@bootlin.com>,
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: Sat, 26 Jul 2025 16:17:45 +0200 [thread overview]
Message-ID: <CACRpkdbjQSns7a9EMx_5kdJ4Y2wsnocTLNsO2es7MQ=rKCBkQw@mail.gmail.com> (raw)
In-Reply-To: <CAMRc=MeZ4HHJGkVBysLyusW5G-rM0iSQV1qqmFJUe1rsZrN2AA@mail.gmail.com>
On Wed, Jul 23, 2025 at 10:43 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> On Tue, Jul 15, 2025 at 3:17 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> > Well, nobody responded to my last email. This is a cross-tree series
> > so at least Linus must confirm he's ok.
> >
> > Bart
>
> Linus, I'm willing to queue at least the GPIO part for v6.17, does the
> pinctrl part look good to you?
Yes go ahead, sorry for late reply!
Acked-by: Linus Walleij <linus.walleij@linaro.org>
I was mainly waiting for Andy's review on this, so if Andy
is OK, I'm OK with it.
Yours,
Linus Walleij
next prev parent reply other threads:[~2025-07-26 14:17 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
2025-07-15 13:17 ` Bartosz Golaszewski
2025-07-23 8:43 ` Bartosz Golaszewski
2025-07-26 14:17 ` Linus Walleij [this message]
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='CACRpkdbjQSns7a9EMx_5kdJ4Y2wsnocTLNsO2es7MQ=rKCBkQw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--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=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=thomas.richard@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®