From: Lee Jones <lee.jones@linaro.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: marek.behun@nic.cz, linux-leds@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: LED Maintainership
Date: Thu, 14 Jul 2022 13:14:19 +0100 [thread overview]
Message-ID: <YtAIm+X2XchcSkFX@google.com> (raw)
In-Reply-To: <20220714112326.GA16407@duo.ucw.cz>
On Thu, 14 Jul 2022, Pavel Machek wrote:
> Hi!
>
> > Not sure what's going on behind the scenes, but it looks as though the
> > LED subsystem has been left unmaintained for at least 2 months now.
>
> > Does anyone have any objection to me stepping in as temporary
> > maintainer until the situation is resolved?
>
> Yes, I'm a bit busy and would not mind help.
>
> There's a lot of easy stuff in the LED -- drivers not introducing new
> APIs -- and some quite tricky stuff -- userland API leaves... a lot to
> be desired, and we are in the middle of defining multicolor API.
>
> I wanted to ask Marek (in cc now) if he would be interested in
> helping. He knows the APIs / issues, and actually has multicolor LEDs
> he cares about. Marek, are you interested?
>
> If Marek is not interested, yes, help with the driver stuff would be
> welcome.
No problem. The offer still stands.
I guess Marek and I aren't mutually exclusive either.
Any harm in us both helping out (if Marek is also interested that is)?
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2022-07-14 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 9:41 LED Maintainership Lee Jones
2022-07-14 10:04 ` Greg Kroah-Hartman
2022-07-14 11:01 ` Andy Shevchenko
2022-07-14 11:23 ` Pavel Machek
2022-07-14 12:14 ` Lee Jones [this message]
2022-07-14 20:25 ` Marek Behún
2022-07-30 21:11 ` Pavel Machek
2022-09-20 8:53 ` Pavel Machek
2022-10-03 9:48 ` 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=YtAIm+X2XchcSkFX@google.com \
--to=lee.jones@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=pavel@ucw.cz \
/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.