[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210728202547.7uvfwflpruku7yps@pengutronix.de>
Date: Wed, 28 Jul 2021 22:25:47 +0200
From: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
To: Stephen Boyd <sboyd@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Claudiu.Beznea@...rochip.com
Cc: Arnd Bergmann <arnd@...db.de>, andy.shevchenko@...il.com,
alexandre.belloni@...tlin.com, Nicolas.Ferre@...rochip.com,
thierry.reding@...il.com, lee.jones@...aro.org,
linux-clk@...r.kernel.org, linux-rtc@...r.kernel.org,
o.rempel@...gutronix.de, Ludovic.Desroches@...rochip.com,
aardelean@...iqon.com, linux-pwm@...r.kernel.org,
broonie@...nel.org, Jonathan.Cameron@...wei.com,
linux-arm-kernel@...ts.infradead.org, a.zummo@...ertech.it,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
wsa@...nel.org, kernel@...gutronix.de, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org
Subject: About clk maintainership [Was: Re: [PULL] Add variants of
devm_clk_get for prepared and enabled clocks enabled clocks]
Hello,
I adapted the Subject in the hope to catch Stephen's and Michael's
attention. My impression is that this thread isn't on their radar yet,
but the topic here seems important enough to get a matching Subject.
On Mon, Jul 26, 2021 at 09:18:16AM +0000, Claudiu.Beznea@...rochip.com wrote:
> > On Fri, Jul 23, 2021 at 11:26:58AM +0300, Andy Shevchenko wrote:
> >> On Thursday, July 22, 2021, Wolfram Sang <wsa@...nel.org> wrote:
> >>>>>> [ some frustration for not getting feedback for clk patches ]
> >>>>> What about adding gkh to the list explaining the situation to him?
> >>>> Greg doesn't like devm_ stuff.
> >>>>
> >>>> I already asked Arnd who doesn't want to interfere and akpm who didn't
> >>>> react either up to now.
> >>> Wow, okay, that is frustrating.
> >> The situation simply shows the process gap and One Maintainer nowadays is
> >> far from enough to satisfy demands.
> >
> > Technically there are two maintainers for drivers/clk, Michael Turquette
> > and Stephen Boyd. It seems Michael is MIA and Stephen doesn't have the
> > capacity to address all requests.
> >
> >> What I think about is that we need to escalate this to Linus and
> >> others and elaborate the mechanisms how to squeeze a new (additional)
> >> maintainer when the original one is not responsive. Let’s say some
> >> procedural steps. Otherwise we doomed because of human factor.
> >
> > Assuming there was some process for this, is there someone who is
> > willing to take responsibility here?
>
> In the last year I worked on AT91 clock drivers and I would be available
> for taking responsibility beyond AT91 clocks (if everyone's OK with this),
> in whatever form the current maintainers and people in the audience would
> agree, if any (co-maintainer or other forms that could be useful). The idea
> is to help things progress as I also have patches waiting for feedback on
> clock mailing list for almost 6 months.
>
> Let me know if I can be helpful.
Wondering about how we can progress here I think it's crucial that
Stephen and/or Michael share their thoughts about how they intend to
care for drivers/clk in the future.
Do you want to keep the maintainer post long-term? Or only for a
transitional period until someone else can take care? Is your
non-presence only temporal and is it foreseeable that you will increase
your efforts in the next weeks/months again? Do you welcome a
co-maintainer? What kind of involvement would you consider helpful?
Thanks to Claudiu for offering to support here, at least from my side
this is very appreciated.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists