From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Brian Masney <bmasney@redhat.com>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ben Dooks" <ben.dooks@codethink.co.uk>,
"Chen-Yu Tsai" <wenst@chromium.org>,
"Felix Gu" <ustc.gu@gmail.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"J. Neuschäfer" <j.ne@posteo.net>,
"Maxime Ripard" <mripard@kernel.org>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
"Shawn Guo" <shawnguo@kernel.org>
Subject: Re: [GIT PULL] clk: round one of improvements for v7.1
Date: Mon, 16 Mar 2026 18:50:34 +0200 [thread overview]
Message-ID: <abg02kmJvZITPdgx@ashevche-desk.local> (raw)
In-Reply-To: <abLV9vjYxXsKciHW@redhat.com>
On Thu, Mar 12, 2026 at 11:04:22AM -0400, Brian Masney wrote:
> Hi Stephen,
>
> Here's a pull for some fixes and improvements for the clk subsystem
> that's been posted over the last month. Details are in the signed git
> tag. I didn't include any new drivers, or changes where it looks like
> there is a submaintainer that typically sends you a pull separately.
>
>
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>
> Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>
> are available in the Git repository at:
>
> https://github.com/masneyb/linux tags/clk-for-stephen-round-1-v7.1
>
> for you to fetch changes up to 5e31ef47fa888c9ce117a85bff6a7df26cb2c337:
>
> clk: scmi: Add i.MX95 OEM extension support for SCMI clock driver (2026-03-12 09:45:03 -0400)
Hmm... CLK tree has not been updating for 3+ weeks.
Should we start being worried?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-03-16 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 15:04 Brian Masney
2026-03-16 16:50 ` Andy Shevchenko [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=abg02kmJvZITPdgx@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=ben.dooks@codethink.co.uk \
--cc=bmasney@redhat.com \
--cc=geert+renesas@glider.be \
--cc=j.ne@posteo.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@oss.nxp.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ustc.gu@gmail.com \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®