LKML Archive on
help / color / mirror / Atom feed
From: Hans de Goede <>
To: Pavel Machek <>, Andy Shevchenko <>
Cc: Linux LED Subsystem <>,
	Linux Kernel Mailing List <>,
	Linus Walleij <>,
	Geert Uytterhoeven <>,
	Pavel Machek <>,
	Greg Kroah-Hartman <>
Subject: Re: LED subsystem lagging maintenance
Date: Wed, 28 Jul 2021 12:44:27 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20210728103551.GA31304@amd>


On 7/28/21 12:35 PM, Pavel Machek 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?
> 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.

It is good to hear that you are still actively maintaining the LED
subsystem, thank you.

This thread does remind me that I was planning on re-sending this
LED patch which seems to have fallen through the cracks:

Can you pick this one up please? Or shall I resend it?



  reply	other threads:[~2021-07-28 10:44 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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: LED subsystem lagging maintenance' \

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