From: Andrew Morton <akpm@linux-foundation.org>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Marcin Juszkiewicz <openembedded@hrw.one.pl>
Subject: Re: Git backlight subsystem tree
Date: Wed, 7 Feb 2007 19:01:53 -0800 [thread overview]
Message-ID: <20070207190153.4acd6006.akpm@linux-foundation.org> (raw)
In-Reply-To: <1170901826.5859.2.camel@localhost.localdomain>
On Thu, 08 Feb 2007 02:30:26 +0000 Richard Purdie <rpurdie@rpsys.net> wrote:
> I'm thinking of more officially volunteering to maintain the Linux
> backlight class/subsystem and have been trying to sort out the various
> pending patches. I've made a backlight tree available as:
>
> http://git.o-hand.com/?p=linux-rpurdie-backlight;a=shortlog;h=for-mm
>
> (or git://git.o-hand.com/linux-rpurdie-backlight)
>
> This has a for-mm branch containing the backlight patches I've sorted
> out so far. I still have some others left to deal with which are
> probably more invasive and will need discussion and testing which I'll
> send some mails about soon.
No probs, I added git://git.o-hand.com/linux-rpurdie-backlight#for-mm to
-mm as git-backlight.patch.
> I'm planning to setup an LED drivers/class tree too, I have a couple of
> pending patches for that.
ooh, patches!
next prev parent reply other threads:[~2007-02-08 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 2:30 Git backlight subsystem tree Richard Purdie
2007-02-08 3:01 ` Andrew Morton [this message]
2007-02-08 15:28 ` James Simmons
2007-02-08 17:59 ` Richard Purdie
2007-02-08 18:32 ` James Simmons
2007-02-08 19:37 ` Richard Purdie
2007-02-08 21:23 ` Greg KH
2007-02-08 21:54 ` James Simmons
2007-02-08 23:41 ` Greg KH
2007-02-08 23:50 ` Richard Purdie
2007-02-09 0:23 ` Greg KH
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=20070207190153.4acd6006.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openembedded@hrw.one.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox