From: Xianwei Zhao <xianwei.zhao@amlogic.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] pinctrl: add support amlogic a9
Date: Fri, 29 May 2026 11:02:11 +0800 [thread overview]
Message-ID: <36cdfa84-1e83-4a44-a529-653d476778fd@amlogic.com> (raw)
In-Reply-To: <CAD++jLmGr_UOja2yHjCHv7xRcGqit_TxKk7A5YzSoviicJrJUA@mail.gmail.com>
Hi Linus,
I don't see these patches in the for-next branch yet. Were they
intentionally left out?
On 2026/5/12 04:26, Linus Walleij wrote:
> On Thu, May 7, 2026 at 10:21 AM Xianwei Zhao via B4 Relay
> <devnull+xianwei.zhao.amlogic.com@kernel.org> wrote:
>
>> Add pinctrl bindings and driver about for amlogic a9.
>>
>> Signed-off-by: Xianwei Zhao<xianwei.zhao@amlogic.com>
> Patches applied!
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2026-05-29 3:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 8:21 [PATCH v2 0/2] pinctrl: add support amlogic a9 Xianwei Zhao via B4 Relay
2026-05-07 8:21 ` [PATCH v2 1/2] dt-bindings: pinctl: amlogic,pinctrl-a4: Add compatible string for A9 Xianwei Zhao via B4 Relay
2026-05-07 17:24 ` Conor Dooley
2026-05-07 8:21 ` [PATCH v2 2/2] pinctrl: meson: support amlogic A9 SoC Xianwei Zhao via B4 Relay
2026-05-11 20:26 ` [PATCH v2 0/2] pinctrl: add support amlogic a9 Linus Walleij
2026-05-29 3:02 ` Xianwei Zhao [this message]
2026-05-29 20:30 ` 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=36cdfa84-1e83-4a44-a529-653d476778fd@amlogic.com \
--to=xianwei.zhao@amlogic.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.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