From: Peter Chen <peter.chen@cixtech.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Gary Yang <gary.yang@cixtech.com>,
Fugang Duan <fugang.duan@cixtech.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
cix-kernel-upstream@cixtech.com
Subject: Re: [PATCH v5 0/3] Add pinctrl support for Sky1
Date: Tue, 28 Oct 2025 09:04:38 +0800 [thread overview]
Message-ID: <aQAWpkIXhsMW6ggo@nchen-desktop> (raw)
In-Reply-To: <CACRpkdZAaEim0yJLkXNctJA0jBFj7LGyTGVvy7_mMf5G+vUWOQ@mail.gmail.com>
On 25-10-27 22:56:56, Linus Walleij wrote:
> EXTERNAL EMAIL
>
> Hi Gary,
>
> On Tue, Oct 21, 2025 at 9:04 AM Gary Yang <gary.yang@cixtech.com> wrote:
>
> > Gary Yang (3):
> > dt-bindings: pinctrl: Add cix,sky1-pinctrl
> > pinctrl: cix: Add pin-controller support for sky1
>
> Patches 1 & 2 applied to the pin control tree for v6.19!
>
> > arm64: dts: cix: Add pinctrl nodes for sky1
>
> This third patch should be applied to the SoC tree, Peter Chen or
> Fugang Duan takes care of that I think? Not sure.
Thanks, Linus.
Yes, since you have applied driver and dt-binding patches, I will
apply Dts patch to CIX SoC Tree.
--
Best regards,
Peter
prev parent reply other threads:[~2025-10-28 1:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 7:04 [PATCH v5 0/3] Add pinctrl support for Sky1 Gary Yang
2025-10-21 7:04 ` [PATCH v5 1/3] dt-bindings: pinctrl: Add cix,sky1-pinctrl Gary Yang
2025-10-22 17:44 ` Conor Dooley
2025-10-21 7:04 ` [PATCH v5 2/3] pinctrl: cix: Add pin-controller support for sky1 Gary Yang
2025-10-21 7:04 ` [PATCH v5 3/3] arm64: dts: cix: Add pinctrl nodes " Gary Yang
2025-10-28 6:08 ` Peter Chen
2025-10-27 21:56 ` [PATCH v5 0/3] Add pinctrl support for Sky1 Linus Walleij
2025-10-28 1:04 ` Peter Chen [this message]
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=aQAWpkIXhsMW6ggo@nchen-desktop \
--to=peter.chen@cixtech.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--cc=gary.yang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).