LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux LED Subsystem <linux-leds@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Hans de Goede <hdegoede@redhat.com>, Pavel Machek <pavel@ucw.cz>,
	Pavel Machek <pavel@denx.de>
Subject: Re: LED subsystem lagging maintenance
Date: Wed, 28 Jul 2021 14:11:58 +0300	[thread overview]
Message-ID: <CAHp75VeDR7NLwhXqBC59EekWK+yp--xe6yhdmn4qH+3L+w88uA@mail.gmail.com> (raw)
In-Reply-To: <YQEzFYPWVdZFqLVC@kroah.com>

On Wed, Jul 28, 2021 at 1:36 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Wed, Jul 28, 2021 at 01:26:20PM +0300, Andy Shevchenko wrote:
> > Hi!
> >
> > I have noticed that in the last couple of cycles the LED subsystem is
> > a bit laggish in terms of maintenance (*). I think it's time that
> > someone can help Pavel to sort things out.
> >
> > In any case, I wonder if we have any kind of procedure for what to do
> > in such cases. Do we need to assume that the subsystem is in a
> > (pre-)orphaned state? If so, who is the best to take care of patch
> > flow?
>
> What outstanding patches have not been handled?  Have you talked to
> Pavel about this?

Pavel has known about them I believe. But just for your convenience
https://lore.kernel.org/linux-leds/20210529111935.3849707-1-andy.shevchenko@gmail.com/T/#u

> > *) e.g. I have a series against a few drivers in LED with actual fixes
> > and it is missed v5.13 (okay, that time Pavel had comments which I
> > have addressed at ~rc7 time frame), missed v5.14 and seems on the
> > curve to miss v5.15.
>
> If you address something at -rc7 you should not expect the changes to be
> merged in time for the next release, what would you do if you were on
> the other end?

Yes, that's why skipping v5.13 is okay, but v5.14 is completely out after that.

> > P.S. I Cc'ed lately active, AFAICS, in that area people + Greg for his opinion.
>
> I think that Pavel should be the one asking for help here if he needs
> it.

I hope so. And we won't see the series dangling for 2 month without
any single word from a maintainer. Thanks for your reply!

-- 
With Best Regards,
Andy Shevchenko

      reply	other threads:[~2021-07-28 11:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 10:26 Andy Shevchenko
2021-07-28 10:35 ` Pavel Machek
2021-07-28 10:44   ` Hans de Goede
2021-08-03 21:58     ` Pavel Machek
2021-08-04  7:29       ` Andy Shevchenko
2021-08-04  7:36         ` Pavel Machek
2021-07-28 11:07   ` Andy Shevchenko
2021-07-28 11:17     ` Pavel Machek
2021-07-28 11:31       ` Andy Shevchenko
2021-07-28 10:36 ` Greg Kroah-Hartman
2021-07-28 11:11   ` Andy Shevchenko [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=CAHp75VeDR7NLwhXqBC59EekWK+yp--xe6yhdmn4qH+3L+w88uA@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@denx.de \
    --cc=pavel@ucw.cz \
    --subject='Re: LED subsystem lagging maintenance' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).