From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: "Sander Vanheule" <sander@svanheule.net>,
"Linus Walleij" <linusw@kernel.org>,
"Andreas Färber" <afaerber@suse.de>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Jeffery <andrew@codeconstruct.com.au>,
linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Joel Stanley <joel@jms.id.au>,
linux-realtek-soc@lists.infradead.org,
James Tai <james.tai@realtek.com>,
Yu-Chun Lin <eleanor.lin@realtek.com>
Subject: Re: [PATCH 3/4] pinctrl: vt8500: Enable compile testing
Date: Mon, 13 Apr 2026 13:12:14 +0200 [thread overview]
Message-ID: <dec1aa54-5bfd-4372-8c5b-983618d48291@oss.qualcomm.com> (raw)
In-Reply-To: <a5e993d2b6c8b57d2057909812ce831877762bd6.camel@svanheule.net>
On 10/04/2026 23:22, Sander Vanheule wrote:
> Hi Krzysztof,
>
> On Fri, 2026-04-10 at 15:04 +0200, Krzysztof Kozlowski wrote:
>> Enable compile testing for Realtek pin controller drivers for increased
>
> Small nit, but this looks like a copy-paste error from the other patch.
>
> Realtek -> VIA/Wondermedia (or vt8500, whatever you prefer)
>
Yes.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-13 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 13:04 [PATCH 0/4] pinctrl: More compile testing Krzysztof Kozlowski
2026-04-10 13:04 ` [PATCH 1/4] pinctrl: realtek: Enable " Krzysztof Kozlowski
2026-04-13 9:49 ` Yu-Chun Lin [林祐君]
2026-04-10 13:04 ` [PATCH 2/4] pinctrl: aspeed: Enable compile testing outside of ARCH_ASPEED Krzysztof Kozlowski
2026-04-10 13:04 ` [PATCH 3/4] pinctrl: vt8500: Enable compile testing Krzysztof Kozlowski
2026-04-10 21:22 ` Sander Vanheule
2026-04-13 11:12 ` Krzysztof Kozlowski [this message]
2026-04-10 13:04 ` [PATCH 4/4] ARM: realtek: MAINTAINERS: Include pin controller drivers Krzysztof Kozlowski
2026-04-13 9:23 ` Yu-Chun Lin [林祐君]
2026-04-13 11:13 ` Krzysztof Kozlowski
2026-04-13 13:57 ` Yu-Chun Lin
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=dec1aa54-5bfd-4372-8c5b-983618d48291@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=afaerber@suse.de \
--cc=andrew@codeconstruct.com.au \
--cc=eleanor.lin@realtek.com \
--cc=james.tai@realtek.com \
--cc=joel@jms.id.au \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sander@svanheule.net \
/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