From: Linus Walleij <linus.walleij@linaro.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] pinctrl: tegra: Add Tegra186 pinmux driver
Date: Fri, 17 Oct 2025 00:17:52 +0200 [thread overview]
Message-ID: <CACRpkdbYkWL4BPyARSOCRQoVHJkTFpDA+Mfo-Aq+-dLGosqJOg@mail.gmail.com> (raw)
In-Reply-To: <CALHNRZ9J2VFLm39wm7+8Le8rt2HpfeHgDOm6mc-s7_Ya8aXe1g@mail.gmail.com>
On Tue, Oct 14, 2025 at 7:54 PM Aaron Kling <webgeek1234@gmail.com> wrote:
> Reminder about this series. Patches 1 and 2 are in v6.18-rc1. Patch 3
> is not. And I have seen no indication that it has been picked up or
> will be picked up within the 6.18 cycle.
Patch 3 is a DTS patch so it should go through the Tegra tree to
the SoC tree, I guess Thierry collects them?
Yours,
Linus Walleij
prev parent reply other threads:[~2025-10-16 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 21:24 Aaron Kling via B4 Relay
2025-08-12 21:24 ` [PATCH v3 1/3] dt-bindings: pinctrl: Document Tegra186 pin controllers Aaron Kling via B4 Relay
2025-08-12 21:24 ` [PATCH v3 2/3] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling via B4 Relay
2025-08-12 21:24 ` [PATCH v3 3/3] arm64: tegra: Add Tegra186 pin controllers Aaron Kling via B4 Relay
2025-09-03 4:06 ` Mikko Perttunen
2025-10-16 15:16 ` Thierry Reding
2025-08-19 11:29 ` [PATCH v3 0/3] pinctrl: tegra: Add Tegra186 pinmux driver Linus Walleij
2025-09-03 4:53 ` Aaron Kling
2025-09-03 6:55 ` Linus Walleij
2025-09-03 17:58 ` Aaron Kling
2025-09-04 13:09 ` Thierry Reding
2025-10-14 17:54 ` Aaron Kling
2025-10-16 22:17 ` Linus Walleij [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=CACRpkdbYkWL4BPyARSOCRQoVHJkTFpDA+Mfo-Aq+-dLGosqJOg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=webgeek1234@gmail.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®