Re: [PATCH v3 00/11] leds: deduplicate led_init_default_state_get()
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: 2022-11-22 13:39:01
Also in:
linux-arm-kernel, linux-leds, linux-mediatek, lkml
On Mon, Nov 14, 2022 at 01:47:58PM +0200, Andy Shevchenko wrote:
On Mon, Nov 14, 2022 at 11:41:31AM +0100, Greg Kroah-Hartman wrote:quoted
On Mon, Nov 14, 2022 at 12:19:29PM +0200, Andy Shevchenko wrote:quoted
On Mon, Nov 14, 2022 at 10:11:25AM +0000, Lee Jones wrote:quoted
On Tue, 08 Nov 2022, Andy Shevchenko wrote:quoted
On Mon, Oct 31, 2022 at 05:32:26PM +0200, Andy Shevchenko wrote:quoted
On Mon, Oct 31, 2022 at 08:53:49AM +0000, Lee Jones wrote:quoted
On Tue, 25 Oct 2022, Andy Shevchenko wrote:quoted
On Tue, Sep 06, 2022 at 04:49:53PM +0300, Andy Shevchenko wrote:quoted
There are several users of LED framework that reimplement the functionality of led_init_default_state_get(). In order to deduplicate them move the declaration to the global header (patch 2) and convert users (patche 3-11).Dear LED maintainers, is there any news on this series? It's hanging around for almost 2 months now...My offer still stands if help is required.From my point of view the LED subsystem is quite laggish lately (as shown by this patch series, for instance), which means that _in practice_ the help is needed, but I haven't got if we have any administrative agreement on that. Pavel?So, Pavel seems quite unresponsive lately... Shall we just move on and take maintainership?I had an off-line conversation with Greg who advised me against that.OK. What the reasonable option we have then?I thought there is now a new LED maintainer, is that not working out?No new (co-)maintainer due to stale mate situation as far as I can read it right now.
So, any suggestion on how to proceed here? De facto we have no patch flow in LED subsystem and the queue is growing... -- With Best Regards, Andy Shevchenko