Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
	Haotian Zhang <vulab@iscas.ac.cn>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: gsbi: fix double disable caused by devm
Date: Mon, 27 Oct 2025 09:09:18 -0500	[thread overview]
Message-ID: <176157405469.8818.1747544601110229644.b4-ty@kernel.org> (raw)
In-Reply-To: <20251020160215.523-1-vulab@iscas.ac.cn>


On Tue, 21 Oct 2025 00:02:15 +0800, Haotian Zhang wrote:
> In the commit referenced by the Fixes tag, devm_clk_get_enabled() was
> introduced to replace devm_clk_get() and clk_prepare_enable(). While
> the clk_disable_unprepare() call in the error path was correctly
> removed, the one in the remove function was overlooked, leading to a
> double disable issue.
> 
> Remove the redundant clk_disable_unprepare() call from gsbi_remove()
> to fix this issue. Since all resources are now managed by devres
> and will be automatically released, the remove function serves no purpose
> and can be deleted entirely.
> 
> [...]

Applied, thanks!

[1/1] soc: qcom: gsbi: fix double disable caused by devm
      commit: 2286e18e3937c69cc103308a8c1d4898d8a7b04f

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2025-10-27 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 16:02 [PATCH] soc: qcom: gsbi: fix double disable caused by devm Haotian Zhang
2025-10-20 16:03 ` kernel test robot
2025-10-21  8:51 ` Konrad Dybcio
2025-10-27 14:09 ` Bjorn Andersson [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=176157405469.8818.1747544601110229644.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vulab@iscas.ac.cn \
    /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