Re: [PATCH v2 2/6] dt-bindings: pinctrl: Document Tegra238 pin controllers

[Krzysztof Kozlowski]

On Mon, Apr 20, 2026 at 10:05:57AM +0000, pshete@xxxxxxxxxx wrote:
> From: Prathamesh Shete <pshete@xxxxxxxxxx>
> 
> Tegra238 contains two pin controllers. Document their
> compatible strings and describe the list of pins and
> functions that they provide.

Please wrap code according to the preferred limit expressed in Kernel
coding style (checkpatch is not a coding style description, but only a
tool).  However don't wrap blindly (see Kernel coding style).

Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830


Really, just try yourself:


b4 diff '20260420100601.343707-3-pshete@xxxxxxxxxx'
Looking up https://lore.kernel.org/all/20260420100601.343707-3-pshete@xxxxxxxxxx/
Checking for older revisions
Grabbing search results from lore.kernel.org
---
Analyzing 22 messages in the thread
WARNING: duplicate messages found at index 1
   Subject 1: pinctrl: tegra: Export tegra_pinctrl_probe()
   Subject 2: arm64: tegra: Add pinctrl nodes for Tegra264
  2 is a reply... replacing existing: arm64: tegra: Add pinctrl nodes for Tegra264
Looking for additional code-review trailers on lore.kernel.org
Analyzing 0 code-review messages
Preparing fake-am for v1: Add Tegra238 and Tegra264 pinctrl support
  range: 59c488f24a80..90c14406cf64
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 upper series v2


Can nvidia finally start using normal/expected process? There are tools
for that for a few years...

Entire Qualcomm, which upstreams magnitude more patches than Nvidia,
uses b4 (basically "must" use otherwise we will complain). Why it cannot
happen here?

Best regards,
Krzysztof