public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: ti: Fix reference imbalance in ti_find_clock_provider
Date: Tue, 23 Aug 2022 14:52:47 +0300	[thread overview]
Message-ID: <YwS/j5ATAfCb1U4l@atomide.com> (raw)
In-Reply-To: <c62649f0-2be1-459c-bfa5-4c94a3e4300f@smile.fr>

* Romain Naour <romain.naour@smile.fr> [220823 09:22]:
> Hello,
> 
> Le 19/08/2022 à 23:23, Stephen Boyd a écrit :
> > Quoting Jan Kiszka (2022-08-08 15:26:58)
> >> From: Jan Kiszka <jan.kiszka@siemens.com>
> >>
> >> When a clock is found via clock-output-names, we need to reference it
> >> explicitly to match of_find_node_by_name behavior. Failing to do so
> >> causes warnings like this:
> >>
> > 
> > Is this superseeded by
> > https://lore.kernel.org/r/20220621091118.33930-1-tony@atomide.com?
> 
> I noticed the same issue and tested separately with both patches.
> 
> Indeed, this patch is not needed anymore with "[PATCH] clk: ti: Fix missing
> of_node_get() ti_find_clock_provider()" applied.

OK good to hear and thanks for testing.

Regards,

Tony

      reply	other threads:[~2022-08-23 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 22:26 [PATCH] clk: ti: Fix reference imbalance in ti_find_clock_provider Jan Kiszka
2022-08-19 21:23 ` Stephen Boyd
2022-08-23  9:29   ` Romain Naour
2022-08-23 11:52     ` Tony Lindgren [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=YwS/j5ATAfCb1U4l@atomide.com \
    --to=tony@atomide.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=romain.naour@smile.fr \
    --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