From: Jerome Brunet <jbrunet@baylibre.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] clk: add a clk_hw helpers to get the clock device or device_node
Date: Mon, 23 Jun 2025 10:34:07 +0200 [thread overview]
Message-ID: <1jo6uekgao.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <175040405169.4372.877329870252746551@lazor> (Stephen Boyd's message of "Fri, 20 Jun 2025 00:20:51 -0700")
On Fri 20 Jun 2025 at 00:20, Stephen Boyd <sboyd@kernel.org> wrote:
> Quoting Jerome Brunet (2025-04-17 06:44:21)
>> This patchset adds helpers to get the device or device_node associated with
>> clk_hw. This can be used by clock drivers to access various device related
>> functionality. The 2nd changes adds kunit test coverage for the new helpers
>>
>
> I've pushed this to clk-hw-device, splitting the test patch into two and
> reworking it. Let me know if you see anything off.
Thanks a lot Stephen !
You could keep the authorship of the 2nd patch I think, it is more a
rewrite than a rework. Either way, it is fine by me. Thanks again.
--
Jerome
prev parent reply other threads:[~2025-06-23 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 13:44 [PATCH 0/2] clk: add a clk_hw helpers to get the clock device or device_node Jerome Brunet
2025-04-17 13:44 ` [PATCH 1/2] " Jerome Brunet
2025-05-05 9:33 ` Jerome Brunet
2025-06-02 16:42 ` Brian Masney
2025-06-20 7:18 ` Stephen Boyd
2025-04-17 13:44 ` [PATCH 2/2] clk: tests: add clk_hw_get_dev() and clk_hw_get_of_node() tests Jerome Brunet
2025-06-02 17:06 ` Brian Masney
2025-06-20 7:18 ` Stephen Boyd
2025-06-02 11:59 ` [PATCH 0/2] clk: add a clk_hw helpers to get the clock device or device_node Jerome Brunet
2025-06-20 7:20 ` Stephen Boyd
2025-06-23 8:34 ` Jerome Brunet [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=1jo6uekgao.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.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