LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Linux LED Subsystem <linux-leds@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: 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>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: LED subsystem lagging maintenance
Date: Wed, 28 Jul 2021 13:26:20 +0300	[thread overview]
Message-ID: <CAHp75VeWKgyz32scczN0c+iJwGZXVP42g0NG0oXrdJ34GyHB8w@mail.gmail.com> (raw)

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?

*) 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.

P.S. I Cc'ed lately active, AFAICS, in that area people + Greg for his opinion.

-- 
With Best Regards,
Andy Shevchenko

             reply	other threads:[~2021-07-28 10:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 10:26 Andy Shevchenko [this message]
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

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=CAHp75VeWKgyz32scczN0c+iJwGZXVP42g0NG0oXrdJ34GyHB8w@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).