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.18
Date: Mon, 15 Sep 2025 18:38:44 -0700 [thread overview]
Message-ID: <175798672445.4354.9868549804401398525@lazor> (raw)
In-Reply-To: <1jecs8hxry.fsf@starbuckisacylon.baylibre.com>
Quoting Jerome Brunet (2025-09-15 02:26:25)
>
> Hi Stephen,
>
> Here are the Amlogic clock updates for v6.18.
>
> This is mostly a clean up of pointless differences between the
> controllers which have been accumulated over the years. Hopefully, this
> will help with the maintenance and simplify the review of the incoming
> new controllers.
>
> Overall, this is just simple stuff but since it touches every Amlogic
> controllers, the diff is fairly large.
>
> Please pull
> Cheers
>
> Jerome
>
> The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
>
> Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
>
> are available in the Git repository at:
>
> https://github.com/BayLibre/clk-meson.git tags/clk-meson-v6.18-1
>
> for you to fetch changes up to 01f3a6d1d59b8e25a6de243b0d73075cf0415eaf:
>
> clk: amlogic: c3-peripherals: use helper for basic composite clocks (2025-09-04 18:27:12 +0200)
>
> ----------------------------------------------------------------
Thanks. Pulled into 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-09-16 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 9:26 [GIT PULL] clk: meson: amlogic updates for v6.18 Jerome Brunet
2025-09-16 1:38 ` 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=175798672445.4354.9868549804401398525@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