From: Stephen Boyd <sboyd@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>,
linux-amlogic <linux-amlogic@lists.infradead.org>
Subject: Re: [GIT PULL] clk: meson: amlogic updates for v6.17
Date: Mon, 21 Jul 2025 10:43:01 -0700 [thread overview]
Message-ID: <175311978158.4111.6766617410857124161@lazor> (raw)
In-Reply-To: <1j7c09pf23.fsf@starbuckisacylon.baylibre.com>
Quoting Jerome Brunet (2025-07-15 09:57:40)
>
> Hi Stephen,
>
> Here are the Amlogic clock updates for v6.17. This one is a bit larger
> than usual. It depends on the changes in your clk-hw-device branch and
> is based on it.
>
> There is the conclusion of a long standing topic around reset drivers in
> clock, this time using the generic helper to create the auxiliary
> device.
>
> There is also the beginning of clean up of the amlogic controllers with
> more coming in future releases.
>
> Nothing is overly complicated in there but it makes quite a large diff
> since it touches all existing controllers.
>
> Please pull.
> Cheers
>
> Jerome
>
> The following changes since commit ac32d031f508e46c19ab38d6ba8b53fc28df9945:
>
> clk: tests: add clk_hw_get_dev() and clk_hw_get_of_node() tests (2025-06-20 00:15:39 -0700)
>
> are available in the Git repository at:
>
> https://github.com/BayLibre/clk-meson.git tags/clk-meson-v6.17-1
>
> for you to fetch changes up to 8a65268500b00ecee5402ef9f80618ff73f30707:
>
> clk: amlogic: s4: remove unused data (2025-07-02 15:38:19 +0200)
>
> ----------------------------------------------------------------
Thanks. Pulled into to clk-next
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2025-07-21 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 16:57 [GIT PULL] clk: meson: amlogic updates for v6.17 Jerome Brunet
2025-07-21 17:43 ` Stephen Boyd [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=175311978158.4111.6766617410857124161@lazor \
--to=sboyd@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=neil.armstrong@linaro.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