From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: Bui Duc Phuc <phucduc.bui@gmail.com>, Bjorn Helgaas <helgaas@kernel.org>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
kwilczynski@kernel.org, Manivannan Sadhasivam <mani@kernel.org>,
Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Vidya Sagar <vidyas@nvidia.com>,
Niklas Cassel <cassel@kernel.org>,
linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO
Date: Mon, 12 Oct 2026 14:08:27 +0530 [thread overview]
Message-ID: <126200fa-49e0-449a-afac-cc08f4a9ecf3@nvidia.com> (raw)
In-Reply-To: <CAABR9nGNoaO-CmTcRvXuMMmGbVSWybKZVBRRZmzQCab_N1EzZA@mail.gmail.com>
On 08/10/26 4:38 pm, Bui Duc Phuc wrote:
> Hi Bjorn,
>
>>
>> For future posts, please match the subject line capitalization style:
>>
>> PCI: tegra194: Use ...
>>
>> And style as "PERST#" in the subject, commit log, and dmesg text to
>> match spec usage.
>>
>> No need to repost just for this; we can tweak these when applying.
>>
>
> Thanks for the review and for pointing this out.
> I'll keep these style details in mind for future posts.
>
> Best regards,
> Phuc
With the subject line capitalization and "PERST#" style fixes,
Reviewed-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
--
nvpublic
next prev parent reply other threads:[~2026-10-12 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:48 phucduc.bui
2026-10-07 10:48 ` [PATCH 2/2] PCI: tegra194: propagate REFCLK select GPIO errors phucduc.bui
2026-10-12 8:36 ` Manikanta Maddireddy
2026-10-12 9:41 ` Bui Duc Phuc
2026-10-07 20:46 ` [PATCH 1/2] PCI: tegra194: use dev_err_probe() for PERST GPIO Bjorn Helgaas
2026-10-08 11:08 ` Bui Duc Phuc
2026-10-12 8:38 ` Manikanta Maddireddy [this message]
2026-10-12 9:38 ` Bui Duc Phuc
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=126200fa-49e0-449a-afac-cc08f4a9ecf3@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=helgaas@kernel.org \
--cc=jonathanh@nvidia.com \
--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=phucduc.bui@gmail.com \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--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®