From: Krzysztof Kozlowski <krzk@kernel.org>
To: pshete@nvidia.com
Cc: linusw@kernel.org, thierry.reding@kernel.org,
jonathanh@nvidia.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, webgeek1234@gmail.com, rosenp@gmail.com,
linux-tegra@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] Add Tegra238 and Tegra264 pinctrl support
Date: Tue, 28 Apr 2026 08:10:31 +0200 [thread overview]
Message-ID: <20260428-terrestrial-elegant-bittern-cafcfc@quoll> (raw)
In-Reply-To: <20260427134231.531222-1-pshete@nvidia.com>
On Mon, Apr 27, 2026 at 01:42:25PM +0000, pshete@nvidia.com wrote:
> From: Prathamesh Shete <pshete@nvidia.com>
>
> Add pinctrl driver support for Tegra238 and Tegra264 along with the
> corresponding device tree binding documentation. Additionally, export
> tegra_pinctrl_probe() to allow the drivers to be built as loadable modules.
>
> Changes in v3:
> - Wrap commit message to 75 chars per line (v2 was too short).
For the record:
b4 diff 20260427134231.531222-1-pshete@nvidia.com
Looking up https://lore.kernel.org/all/20260427134231.531222-1-pshete@nvidia.com/
Grabbing thread from lore.kernel.org/all/20260427134231.531222-1-pshete@nvidia.com/t.mbox.gz
Checking for older revisions
Grabbing search results from lore.kernel.org
Added from v2: 6 patches
---
Analyzing 27 messages in the thread
Preparing fake-am for v2: pinctrl: tegra: Export tegra_pinctrl_probe()
ERROR: v2 series incomplete; unable to create a fake-am range
---
Could not create fake-am range for lower series v2
When we ask to use standard process to send patches, we ask for this for
a reason.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-28 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 13:42 [PATCH v3 0/6] Add Tegra238 and Tegra264 pinctrl support pshete
2026-04-27 13:42 ` [PATCH v3 1/6] pinctrl: tegra: Export tegra_pinctrl_probe() pshete
2026-04-27 13:42 ` [PATCH v3 2/6] dt-bindings: pinctrl: Document Tegra238 pin controllers pshete
2026-04-29 6:40 ` Krzysztof Kozlowski
2026-04-27 13:42 ` [PATCH v3 3/6] pinctrl: tegra: Add Tegra238 pinmux driver pshete
2026-04-27 13:42 ` [PATCH v3 4/6] dt-bindings: pinctrl: Document Tegra264 pin controllers pshete
2026-04-29 6:41 ` Krzysztof Kozlowski
2026-04-27 13:42 ` [PATCH v3 5/6] pinctrl: tegra: Add Tegra264 pinmux driver pshete
2026-04-27 13:42 ` [PATCH v3 6/6] arm64: tegra: Add pinctrl nodes for Tegra264 pshete
2026-04-28 6:10 ` Krzysztof Kozlowski [this message]
2026-04-29 9:38 ` [PATCH v3 0/6] Add Tegra238 and Tegra264 pinctrl support Jon Hunter
2026-05-14 8:17 ` Jon Hunter
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=20260428-terrestrial-elegant-bittern-cafcfc@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=thierry.reding@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.