From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Frank Li <Frank.li@nxp.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH v2 1/2] thermal/drivers/qoriq: Use dev_err_probe() simplify the code
Date: Tue, 18 Feb 2025 19:51:05 +0100 [thread overview]
Message-ID: <5f7f39b9-5cf8-4ebe-816f-d56e52bc7408@linaro.org> (raw)
In-Reply-To: <Z7TEGQQ/JM/q454F@lizhi-Precision-Tower-5810>
On 18/02/2025 18:32, Frank Li wrote:
> On Wed, Jan 22, 2025 at 06:41:22PM +0100, Daniel Lezcano wrote:
>> Hi Frank,
>>
>> On 22/01/2025 16:52, Frank Li wrote:
>>> On Mon, Dec 09, 2024 at 11:48:58AM -0500, Frank Li wrote:
>>>> Use dev_err_probe() and devm_clk_get_optional_enabled() to simplify the
>>>> code.
>>>>
>>>> Signed-off-by: Frank Li <Frank.Li@nxp.com>
>>
>> I applied the patches, thanks
>>
>
> Thanks, I have not seen at linux-next/master. Anything missed?
No, it is in the thermal/bleeding-edge ATM and will go through
thermal/linux-next tomorrow.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2025-02-18 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 16:48 [PATCH v2 1/2] thermal/drivers/qoriq: Use dev_err_probe() simplify the code Frank Li
2024-12-09 16:48 ` [PATCH v2 2/2] thermal/drivers/qoriq: Power down TMU on system suspend Frank Li
2025-01-22 15:52 ` [PATCH v2 1/2] thermal/drivers/qoriq: Use dev_err_probe() simplify the code Frank Li
2025-01-22 17:41 ` Daniel Lezcano
2025-02-18 17:32 ` Frank Li
2025-02-18 18:51 ` Daniel Lezcano [this message]
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=5f7f39b9-5cf8-4ebe-816f-d56e52bc7408@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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