The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: Michael Turquette <mturquette@baylibre.com>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
	"Uwe Kleine-König" <ukleinek@kernel.org>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Jérôme Brunet" <jbrunet@baylibre.com>
Subject: Re: [PATCH] MAINTAINERS: Add myself as co-maintainer for clk subsystem
Date: Fri, 7 Aug 2026 07:16:29 -0400	[thread overview]
Message-ID: <anW-jTldkWSJK3wl@redhat.com> (raw)
In-Reply-To: <CAEG3pNBFyg1uWwDiy8Bd1NKJL4VMOKCvy=_VxoKw+eO_hAdVKw@mail.gmail.com>

Hi Mike,

On Thu, Aug 06, 2026 at 09:55:04PM -0700, Michael Turquette wrote:
> On Tue, Aug 4, 2026 at 8:33 AM Brian Masney <bmasney@redhat.com> wrote:
> >
> > With Michael Turquette stepping down as a clk co-maintainer, this
> > subsystem is big enough that it needs multiple people to keep the
> > clk community healthy. I've already been doing a lot of work to
> > help with clk maintenance, so let's make it official in the MAINTAINERS
> > file.
> 
> Acked-by: Michael Turquette <mturquette@baylibre.com>
> 
> If someone doesn't pick this up and give you commit access to the
> linux-clk tree on git.kernel.org then let me know and I'll unvault my
> SSH key and merge the patch myself. I'm only a bit embarrassed to say
> that it would be nontrivial for me to blow the cobwebs off and commit
> a patch to kernel.org after all of these years ...
> 
> I would also propose to add Jérôme Brunet <jbrunet@baylibre.com> as a
> co-maintainer. This was proposed a long time ago and there was every
> reason to add him, but I was inactive at the time of the proposal and
> nothing changed. I'd like to make this right by proposing him to join
> the clk co-maintainer team now and help you with the load.

Yes, it would be great to have Jérôme help with co-maintainer to help
spread the load. I'll send a v2 that includes him as well.

Mike/Jérôme/Stephen: Will you all be at Linux Plumbers in Prague this
October? I'll be there. I submitted a talk about the CCF to go over the
current state of sync state, how to land my series to fix the clk scaling
issues, and to discuss ideas for how to replace the global prepare lock
with a more fine grained one.

Brian


      reply	other threads:[~2026-08-07 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 15:32 [PATCH] MAINTAINERS: Add myself as co-maintainer for clk subsystem Brian Masney
2026-08-07  4:55 ` Michael Turquette
2026-08-07 11:16   ` Brian Masney [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=anW-jTldkWSJK3wl@redhat.com \
    --to=bmasney@redhat.com \
    --cc=jbrunet@baylibre.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=ukleinek@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