Linux clock framework development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Brian Masney <bmasney@redhat.com>,
	 Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: clk maintenance [Was: Re: [PATCH v1] clk: Use named initializers for platform_device_id arrays]
Date: Sat, 18 Jul 2026 19:13:11 +0200	[thread overview]
Message-ID: <aluuES750vojgH3q@monoceros> (raw)
In-Reply-To: <alpC8l8qPFL955ZB@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]

Hello Brian, Michael and Stephen,

[I trimmed recipients as the new topic isn't related only to my patch
under discussion in this thread.]

On Fri, Jul 17, 2026 at 10:57:54AM -0400, Brian Masney wrote:
> On Fri, Jul 17, 2026 at 11:51:17AM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> > Do you still have it on your radar?
> 
> I sent Stephen a pull on June 29th for stuff that I felt was missed during
> the last merge window and I included 4 of your patches in that pull:
> 
> https://lore.kernel.org/linux-clk/akLzCVzbMbUsgDda@redhat.com/T/#u
> 
> I haven't heard from Stephen yet. There's 2-3 other pulls waiting as
> well.

I only occasionally have clk patches, but my impression is that getting
feedback takes quite long and without Brian's efforts also things would
get lost. (Thanks Brian for picking up my stuff!)

Looking at the current maintainers:

	$ git log --format=fuller --since 2026-01-01 next-20260717 drivers/clk | grep -E 'Boyd|Turquette' | sort | uniq -c
	      8     Acked-by: Stephen Boyd <sboyd@kernel.org>
	     28 Author:     Stephen Boyd <sboyd@kernel.org>
	      3     Cc: Michael Turquette <mturquette@baylibre.com>
	      3     Cc: Stephen Boyd <sboyd@kernel.org>
	     81 Commit:     Stephen Boyd <sboyd@kernel.org>
	      1     Pull clk fix from Stephen Boyd:
	      3     Pull clk updates from Stephen Boyd:
	     54     Signed-off-by: Stephen Boyd <sboyd@kernel.org>
	linux$ git log --format=oneline --since 2026-01-01 next-20260717 drivers/clk | wc -l
	453

(Maybe that is because Stephen cares for the core mostly and arch
maintainers merge stuff about their clks themselves?)

The last commit where Michael Turquette was actively involved is from
2021 (a331659e32718b31f3a304d7797a77d31610468c) which is also the last
mail from him on the clk list (see
https://lore.kernel.org/linux-clk/?q=f%3ATurquette).

I only observe from the side line, but with the relevance of the clk
subsystem I feel maintenance is underpowered today.

Is it time for Michael to step down? Would Brian be ready to become a
full maintainer? Is there a need for more reviewers? Any volunteers to
step up?

Best regards
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-07-18 17:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 10:29 [PATCH v1] clk: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-05-28 10:41 ` Tudor Ambarus
2026-05-28 10:53 ` Peter Griffin
2026-05-28 15:01 ` Brian Masney
2026-05-29  7:27 ` Matti Vaittinen
2026-07-17  9:51 ` Uwe Kleine-König (The Capable Hub)
2026-07-17 14:57   ` Brian Masney
2026-07-18 17:13     ` Uwe Kleine-König (The Capable Hub) [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=aluuES750vojgH3q@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=bmasney@redhat.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