From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
bhelgaas@google.com, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
jingoohan1@gmail.com, vidyas@nvidia.com, cassel@kernel.org,
18255117159@163.com
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [V5,00/13] Fixes to pcie-tegra194 driver
Date: Mon, 9 Feb 2026 14:28:21 +0530 [thread overview]
Message-ID: <0d900dc7-38b1-44e0-a42a-eee83b54b2c6@nvidia.com> (raw)
In-Reply-To: <cf87856e-13f9-4d94-aa07-eed7fb4a2309@kernel.org>
On 09/02/26 1:16 pm, Krzysztof Kozlowski wrote:
> 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
Apologies, I was using 'git format-patch -vX', but I got confused by how
the subject appears on the
https://patchwork.kernel.org/project/linux-pci/list/
and mistakenly removed the “PATCH” prefix from the subject line.
I’ll make sure not to repeat this mistake.
Thanks,
Manikanta
next prev parent reply other threads:[~2026-02-09 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 18:07 Manikanta Maddireddy
2026-02-08 18:07 ` [V5,01/13] PCI: tegra194: Fix polling delay for L2 state Manikanta Maddireddy
2026-02-08 18:07 ` [V5,02/13] PCI: tegra194: Refactor LTSSM state polling on surprise down Manikanta Maddireddy
2026-02-10 17:08 ` Jon Hunter
2026-02-08 18:07 ` [V5,03/13] PCI: tegra194: Don't force the device into the D0 state before L2 Manikanta Maddireddy
2026-02-10 17:10 ` Jon Hunter
2026-02-08 18:07 ` [V5,04/13] PCI: tegra194: Free up EP resources during remove() Manikanta Maddireddy
2026-02-08 18:07 ` [V5,05/13] PCI: tegra194: Use HW version number Manikanta Maddireddy
2026-02-08 18:07 ` [V5,06/13] PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on Manikanta Maddireddy
2026-02-08 18:07 ` [V5,07/13] PCI: tegra194: Disable PERST IRQ only in Endpoint mode Manikanta Maddireddy
2026-02-08 18:07 ` [V5,08/13] PCI: tegra194: Disable direct speed change for EP Manikanta Maddireddy
2026-02-08 18:07 ` [V5,09/13] PCI: tegra194: Use devm_gpiod_get_optional() to parse "nvidia,refclk-select" Manikanta Maddireddy
2026-02-08 18:07 ` [V5,10/13] PCI: tegra194: Apply pinctrl settings for both PCIe RP and EP Manikanta Maddireddy
2026-02-08 18:07 ` [V5,11/13] PCI: tegra194: Free resources during controller deinitialization Manikanta Maddireddy
2026-02-08 18:07 ` [V5,12/13] PCI: tegra194: Allow system suspend when the Endpoint link is not up Manikanta Maddireddy
2026-02-08 18:07 ` [V5,13/13] PCI: tegra194: Set LTR message request before PCIe link up Manikanta Maddireddy
2026-02-09 7:46 ` [V5,00/13] Fixes to pcie-tegra194 driver Krzysztof Kozlowski
2026-02-09 8:58 ` Manikanta Maddireddy [this message]
2026-02-10 17:18 ` 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=0d900dc7-38b1-44e0-a42a-eee83b54b2c6@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.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®