Linux clock framework development
 help / color / mirror / Atom feed
From: Brian Masney <bmasney@redhat.com>
To: Michael Turquette <mturquette@baylibre.com>
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
	"Stephen Boyd" <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, "Jérôme Brunet" <jbrunet@baylibre.com>
Subject: Re: [PATCH] Drop Michael Turquette's clk maintainer entry
Date: Fri, 7 Aug 2026 07:17:11 -0400	[thread overview]
Message-ID: <anW-twyN9XccL2pO@redhat.com> (raw)
In-Reply-To: <CAEG3pNBTOHz59qN08AKJ1p3yXtB3E=8veq1LN8nyQMx2iGKMHg@mail.gmail.com>

On Thu, Aug 06, 2026 at 09:57:57PM -0700, Michael Turquette wrote:
> On Tue, Aug 4, 2026 at 8:57 AM Brian Masney <bmasney@redhat.com> wrote:
> >
> > On Sun, Aug 02, 2026 at 06:34:06PM -0500, Michael Turquette wrote:
> > > On Wed, Jul 29, 2026 at 7:16 AM Uwe Kleine-König <ukleinek@kernel.org> wrote:
> > > >
> > > > Mike wasn't publically active for the clk subsystem since years. Stop
> > > > pretending that there is a maintainer team caring for clk.
> > >
> > > I was hoping to send this patch myself, and to recommend a couple of
> > > folks for promotion to the clk subsystem. Alas, you beat me to the
> > > first half of my plan.
> > >
> > > >
> > > > Signed-off-by: Uwe Kleine-König <ukleinek@kernel.org>
> > >
> > > Acked-by: Michael Turquette <mturquette@baylibre.com>
> >
> > Thanks Mike for everything you have done over the years with linux-clk.
> >
> > I posted this patch to make me co-maintainer to help out Stephen:
> >
> > https://lore.kernel.org/linux-clk/20260804-clk-masney-maintainer-v1-1-de593189a9a1@redhat.com/T/#u
> >
> > To help make this subsystem more sustainable from a maintenance
> > standpoint, I propose:
> >
> > - To push more vendors to participate in meaningful reviews, and send in pulls.
> >   A recent example of where I did that is with Mediatek:
> >   https://lore.kernel.org/linux-clk/amuWdRD-TBQtFT_4@redhat.com/
> >
> > - Try to find more people to help with the subsystem as a whole so that
> >   this all isn't on just one person.
> 
> I acked that patch. Per your second proposal I also suggest that
> Jerome Brunet join you on the team. This is something that should have
> happened forever ago and it's my fault it did not.

Just to close this thread, adding Jerome sounds good. I added more
details to that patch.

Brian


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 12:16 [PATCH] Drop Michael Turquette's clk maintainer entry Uwe Kleine-König
2026-08-02 23:34 ` Michael Turquette
2026-08-04 15:57   ` Brian Masney
2026-08-07  4:57     ` Michael Turquette
2026-08-07 11:17       ` 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-twyN9XccL2pO@redhat.com \
    --to=bmasney@redhat.com \
    --cc=jbrunet@baylibre.com \
    --cc=linux-clk@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