From: Manivannan Sadhasivam <mani@kernel.org>
To: "Vignesh Raghavendra" <vigneshr@ti.com>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-omap@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Anand Moon" <linux.amoon@gmail.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH v3 0/2] PCI: j721e: A couple of cleanups
Date: Fri, 31 Oct 2025 14:23:20 +0530 [thread overview]
Message-ID: <176190080005.8740.2017130135799803682.b4-ty@kernel.org> (raw)
In-Reply-To: <20251028154229.6774-1-linux.amoon@gmail.com>
On Tue, 28 Oct 2025 21:12:22 +0530, Anand Moon wrote:
> Refactor the J721e probe function to use devres helpers for resource
> management. This replaces manual clock handling with
> devm_clk_get_optional_enabled() and assigns the reset GPIO directly
> to the struct members, eliminating unnecessary local variables.
>
> These patches have been compile-tested only, as I do not have access
> to the hardware for runtime verification.
>
> [...]
Applied, thanks!
[1/2] PCI: j721e: Use devm_clk_get_optional_enabled() to get the clock
commit: 59ba8c0981e73cb2bb70074be4ef46b4188424ea
[2/2] PCI: j721e: Use inline reset GPIO assignment and drop local variable
commit: 8895c0fc0671f38746ee1c02b728b126f7dbbf97
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
next prev parent reply other threads:[~2025-10-31 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 15:42 Anand Moon
2025-10-28 15:42 ` [PATCH v3 1/2] PCI: j721e: Use devm_clk_get_optional_enabled() to get the clock Anand Moon
2025-10-28 15:42 ` [PATCH v3 2/2] PCI: j721e: Use inline reset GPIO assignment and drop local variable Anand Moon
2025-10-28 19:58 ` [PATCH v? " Markus Elfring
2025-10-28 17:00 ` [PATCH v3 0/2] PCI: j721e: A couple of cleanups Anand Moon
2025-10-28 19:51 ` [PATCH v? " Markus Elfring
2025-10-30 5:13 ` Anand Moon
2025-10-31 8:53 ` Manivannan Sadhasivam [this message]
2025-11-13 18:26 ` [PATCH v3 " Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2025-10-27 9:03 Anand Moon
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=176190080005.8740.2017130135799803682.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=bhelgaas@google.com \
--cc=dan.carpenter@linaro.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.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®