[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cf87856e-13f9-4d94-aa07-eed7fb4a2309@kernel.org>
Date: Mon, 9 Feb 2026 08:46:54 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Manikanta Maddireddy <mmaddireddy@...dia.com>, bhelgaas@...gle.com,
lpieralisi@...nel.org, kwilczynski@...nel.org, mani@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
thierry.reding@...il.com, jonathanh@...dia.com, jingoohan1@...il.com,
vidyas@...dia.com, cassel@...nel.org, 18255117159@....com
Cc: linux-pci@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [V5,00/13] Fixes to pcie-tegra194 driver
On 08/02/2026 19:07, Manikanta Maddireddy wrote:
> This series[1] was originally posted by Vidya Sagar, and I have rebased
> it onto 6.19.0-rc6-next. I addressed review comments and split this into
> two series, one for fixes(current) and the other is for enhancements.
> I verified these patches on Jetson AGX Orin(Tegra234 SoC).
>
> I added below four new patches to fix bugs, commit message of each
> patch has the details on the bug and fix.
> - PCI: tegra194: Use HW version number
> - PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on
> - PCI: tegra194: Disable PERST IRQ only in Endpoint mode
>
Please use standard email subjects, so with the PATCH keyword in the
title. `git format-patch -vX` helps here to create proper versioned
patches. Another useful tool is b4. Skipping the PATCH keyword makes
filtering of emails more difficult thus making the review process less
convenient.
I really do not get why such big patchset is still not with b4, but if
you insist, then at least do it correct.
Best regards,
Krzysztof
Powered by blists - more mailing lists