From: Pavel Machek <pavel@ucw.cz>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
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@denx.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: LED subsystem lagging maintenance
Date: Wed, 28 Jul 2021 12:35:52 +0200 [thread overview]
Message-ID: <20210728103551.GA31304@amd> (raw)
In-Reply-To: <CAHp75VeWKgyz32scczN0c+iJwGZXVP42g0NG0oXrdJ34GyHB8w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
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?
To be honest, patches were not applied because they were not that
important to begin with, because of lacking explanation, and because
you pushed a bit too hard.
Yes, I'm quite busy in -rc1 to -rc3 timeframe with stable reviews. No,
LED subsystem is not orphaned.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2021-07-28 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 10:26 LED subsystem lagging maintenance Andy Shevchenko
2021-07-28 10:35 ` Pavel Machek [this message]
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=20210728103551.GA31304@amd \
--to=pavel@ucw.cz \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.