From: Stephen Boyd <sboyd@kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] clk: ti: Fix reference imbalance in ti_find_clock_provider
Date: Fri, 19 Aug 2022 14:23:35 -0700 [thread overview]
Message-ID: <20220819212337.AECB9C433D6@smtp.kernel.org> (raw)
In-Reply-To: <63d9211f-d5ce-562e-358a-50f26c7caf35@siemens.com>
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?
next prev parent reply other threads:[~2022-08-19 21:23 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 [this message]
2022-08-23 9:29 ` Romain Naour
2022-08-23 11:52 ` Tony Lindgren
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=20220819212337.AECB9C433D6@smtp.kernel.org \
--to=sboyd@kernel.org \
--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=tony@atomide.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