From: Wolfram Sang <w.sang@pengutronix.de>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Bryan Wu <bryan.wu@canonical.com>,
rpurdie@rpsys.net, linux-kernel@vger.kernel.org,
arnd.bergmann@linaro.org
Subject: Re: [PATCH] MAINTAINERS: Add maintainer for LED subsystem
Date: Sat, 12 May 2012 19:08:30 +0200 [thread overview]
Message-ID: <20120512170830.GN20673@pengutronix.de> (raw)
In-Reply-To: <1336840108.17605.14.camel@joe2Laptop>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
On Sat, May 12, 2012 at 09:28:28AM -0700, Joe Perches wrote:
> On Sat, 2012-05-12 at 12:25 +0200, Wolfram Sang wrote:
> > > If/when patchwork.kernel.org is back up,
> > > that'd be another mechanism to automate
> > > patch notifications for drivers/leds/.
> >
> > http://patchwork.ozlabs.org/ is still there.
>
> but is lkml tracked there?
Well, no, but when a linux-led mailinglist will exist, then it could use
the above service and does not have to wait for kernel.org. That's what
I meant.
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-05-12 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 0:26 [PATCH] MAINTAINERS: Add maintainer for LED subsystem Bryan Wu
2012-05-10 12:45 ` Richard Purdie
2012-05-10 13:57 ` Arnd Bergmann
2012-05-10 18:19 ` Andrew Morton
2012-05-10 18:27 ` Joe Perches
2012-05-12 10:25 ` Wolfram Sang
2012-05-12 16:28 ` Joe Perches
2012-05-12 17:08 ` Wolfram Sang [this message]
2012-05-10 18:36 ` Bryan Wu
2012-05-10 18:53 ` Andrew Morton
2012-05-11 4:29 ` Tim Gardner
2012-05-11 6:30 ` Bryan Wu
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=20120512170830.GN20673@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=arnd.bergmann@linaro.org \
--cc=bryan.wu@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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.