Linux clock framework development
 help / color / mirror / Atom feed
From: "Onur Özkan" <work@onurozkan.dev>
To: Brian Masney <bmasney@redhat.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	mturquette@baylibre.com, sboyd@kernel.org,
	daniel.almeida@collabora.com
Subject: Re: [PATCH v2] clk: devres: fix cleanup in devm_clk_get_optional_enabled_with_rate()
Date: Thu,  3 Sep 2026 10:41:08 +0300	[thread overview]
Message-ID: <20260903074110.101285-1-work@onurozkan.dev> (raw)
In-Reply-To: <apib9XCsTNGA3-u3@redhat.com>

On Wed, 02 Sep 2026 17:58:13 -0400
Brian Masney <bmasney@redhat.com> wrote:

> Hi Onur,
> 
> On Sun, Aug 09, 2026 at 12:54:04PM +0300, Onur Özkan wrote:
> > devm_clk_get_optional_enabled_with_rate() registers its cleanup action
> > before setting the clock rate. If setting the rate fails, it attempts to
> > disable and unprepare a clock that was never enabled. This issue was
> > spotted while reviewing "rust: clk: add devres-managed clks" [1].
> > 
> > Register the cleanup action only after successfully preparing and enabling
> > the clock.
> > 
> > [1]: https://lore.kernel.org/rust-for-linux/20260706-clk-type-state-v5-3-67c5f326a16c@collabora.com
> > 
> > Fixes: 9934a1bd45b2 ("clk: provide devm_clk_get_optional_enabled_with_rate()")
> > Reviewed-by: Brian Masney <bmasney@redhat.com>
> > Signed-off-by: Onur Özkan <work@onurozkan.dev>
> 
> This series no longer applies against the latest clk-next branch. Can you
> rebase this, and submit a new version? I'll be able to pick it up quickly.
> 
> Thanks,
> 
> Brian
> 

Hi Brian,

It seems that the fix has already been applied, but v1 was picked instead of v2.
I sent v2 the next day after receiving warnings from the kernel bot [1], at
which point v1 had not yet been applied anywhere.

[1]: https://lore.kernel.org/all/202608090025.dwxdfqFr-lkp@intel.com

So this patch itself is no longer necessary since the fix is already there. If
you still want to get rid of the warnings I can send another patch for it.

- Onur

  reply	other threads:[~2026-09-03  7:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09  9:54 [PATCH v2] clk: devres: fix cleanup in devm_clk_get_optional_enabled_with_rate() Onur Özkan
2026-09-02 21:58 ` Brian Masney
2026-09-03  7:41   ` Onur Özkan [this message]
2026-09-03 15:37     ` Brian Masney

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=20260903074110.101285-1-work@onurozkan.dev \
    --to=work@onurozkan.dev \
    --cc=bmasney@redhat.com \
    --cc=daniel.almeida@collabora.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    /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