From: Thomas Richard <thomas.richard@bootlin.com>
To: GaryWang <is0124@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy@kernel.org>,
Linus Walleij <linusw@kernel.org>
Cc: Daniele Cleri <danielecleri@aaeon.eu>,
JunYingLai <junyinglai@aaeon.com.tw>,
Louis Chen <louischen@aaeon.com.tw>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] pinctrl: upboard: add device id INTC1055 based UP boards support
Date: Mon, 15 Jun 2026 10:01:25 +0200 [thread overview]
Message-ID: <d6453a9c-d2f1-4aef-8caf-e351c210d6bb@bootlin.com> (raw)
In-Reply-To: <20260612-upboard-pinctrl-add-upboard-intc1055-support-v2-2-4111b256c840@gmail.com>
Hello Gary,
On 6/12/26 12:13 PM, GaryWang wrote:
> Add support "UP Xtreme i12", "UP Squared Pro 7000", "UP Squared i12",
> "UP 7000" boards and I2C/PWM/UART/SPI pins mapping data.
>
Reviewed-by: Thomas Richard <thomas.richard@bootlin.com>
Best Regards,
Thomas
next prev parent reply other threads:[~2026-06-15 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 10:13 [PATCH v2 0/2] upboard pinctrl support for device id INTC1055 GaryWang
2026-06-12 10:13 ` [PATCH v2 1/2] pinctrl: tigerlake: add some pin groups and functions for INTC1055 GaryWang
2026-06-12 10:13 ` [PATCH v2 2/2] pinctrl: upboard: add device id INTC1055 based UP boards support GaryWang
2026-06-15 8:01 ` Thomas Richard [this message]
2026-06-15 9:37 ` Thomas Richard
2026-06-15 11:23 ` GaryWang
2026-06-15 12:13 ` Thomas Richard
2026-06-15 4:35 ` [PATCH v2 0/2] upboard pinctrl support for device id INTC1055 Mika Westerberg
2026-06-15 7:01 ` GaryWang
2026-06-15 9:47 ` Mika Westerberg
2026-06-15 12:32 ` Linus Walleij
2026-06-15 14:07 ` Andy Shevchenko
2026-06-15 14:25 ` GaryWang
2026-06-15 15:00 ` Andy Shevchenko
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=d6453a9c-d2f1-4aef-8caf-e351c210d6bb@bootlin.com \
--to=thomas.richard@bootlin.com \
--cc=andy@kernel.org \
--cc=danielecleri@aaeon.eu \
--cc=is0124@gmail.com \
--cc=junyinglai@aaeon.com.tw \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louischen@aaeon.com.tw \
--cc=mika.westerberg@linux.intel.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