[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALHNRZ-dRvaN_SyHRfAsq2MO-ec8rzkeCy6CtJpYdWTobf1-Wg@mail.gmail.com>
Date: Tue, 2 Sep 2025 23:53:59 -0500
From: Aaron Kling <webgeek1234@...il.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>, Bartosz Golaszewski <brgl@...ev.pl>, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/3] pinctrl: tegra: Add Tegra186 pinmux driver
On Tue, Aug 19, 2025 at 6:30 AM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> On Tue, Aug 12, 2025 at 11:24 PM Aaron Kling via B4 Relay
> <devnull+webgeek1234.gmail.com@...nel.org> wrote:
>
> > This series adds support for Tegra186 pin control, based on a downstream
> > driver, updated to match the existing Tegra194 driver.
> >
> > Signed-off-by: Aaron Kling <webgeek1234@...il.com>
> (...)
> > Aaron Kling (3):
> > dt-bindings: pinctrl: Document Tegra186 pin controllers
> > pinctrl: tegra: Add Tegra186 pinmux driver
>
> These two applied to the pin control git tree.
On patch 3, Mikko noted that I accidentally amended the formatting
changes intended for patch 2 into patch 3. Linus, since you've already
picked this up to your tree, is it too late to fix this properly in a
new revision? It doesn't appear to have made it to the main tree yet.
Or do I need to send in a fixup?
Aaron
Powered by blists - more mailing lists