LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	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>,
	Pavel Machek <pavel@denx.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: LED subsystem lagging maintenance
Date: Tue, 3 Aug 2021 23:58:21 +0200	[thread overview]
Message-ID: <20210803215821.GE30387@amd> (raw)
In-Reply-To: <179c4bce-ce9b-c9a8-4f24-cb4b3397e0f0@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1204 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.
> 
> 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:
> 
> https://lore.kernel.org/alsa-devel/20210221115208.105203-1-hdegoede@redhat.com/
> 
> Can you pick this one up please? Or shall I resend it?

Thanks, applied.

							Pavel
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2021-08-03 21:58 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 [this message]
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=20210803215821.GE30387@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 \
    --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).