From: Viresh Kumar <viresh.kumar@linaro.org>
To: Haoxiang Li <haoxiang_li2024@163.com>
Cc: rafael@kernel.org, zhongqiu.han@oss.qualcomm.com,
hector.yuan@mediatek.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] cpufreq: mediatek-hw: Fix initialization resource leaks
Date: Thu, 19 Nov 2026 16:32:41 +0530 [thread overview]
Message-ID: <av7XUQCgTkhJB43V@vireshk-B250M-D3H> (raw)
In-Reply-To: <20261119052811.2877720-1-haoxiang_li2024@163.com>
On 19-11-26, 13:28, Haoxiang Li wrote:
> This series fixes two resource cleanup omissions introduced by commit
> d776790a5536 ("cpufreq: mediatek-hw: Fix double devm_remap in hotplug case").
>
> Patch 1 releases the resources when the CPUFreq hardware fails to become
> enabled.
>
> Following Zhongqiu's suggestion during review, patch 2 handles the
> additional failure path where mtk_cpu_create_freq_table() fails after
> the registers have been mapped and the memory region requested.
> Thanks to Zhongqiu for pointing out this omission and suggesting a
> separate fix.
>
> Changes in v2:
> - Keep the original hardware enable failure fix unchanged as patch 1.
> - Add patch 2 to clean up on frequency table creation failure, using
> the same Fixes tag.
>
> Haoxiang Li (2):
> cpufreq: mediatek-hw: Release resources when hardware enable fails
> cpufreq: mediatek-hw: Clean up on frequency table creation failure
Applied. Thanks.
--
viresh
prev parent reply other threads:[~2026-11-19 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 5:28 Haoxiang Li
2026-11-19 5:28 ` [PATCH v2 1/2] cpufreq: mediatek-hw: Release resources when hardware enable fails Haoxiang Li
2026-11-19 5:28 ` [PATCH v2 2/2] cpufreq: mediatek-hw: Clean up on frequency table creation failure Haoxiang Li
2026-11-19 10:23 ` [PATCH v2 0/2] cpufreq: mediatek-hw: Fix initialization resource leaks Zhongqiu Han
2026-11-19 11:02 ` Viresh Kumar [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=av7XUQCgTkhJB43V@vireshk-B250M-D3H \
--to=viresh.kumar@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=haoxiang_li2024@163.com \
--cc=hector.yuan@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael@kernel.org \
--cc=zhongqiu.han@oss.qualcomm.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®