From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Richard Purdie" <rpurdie@rpsys.net>
Cc: "Trent Piepho" <xyzzy@speakeasy.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Guennadi Liakhovetski" <lg@denx.de>
Subject: Re: [GIT PULL] LED updates for 2.6.29
Date: Sat, 10 Jan 2009 17:33:26 -0700 [thread overview]
Message-ID: <fa686aa40901101633r71a143cam21e954d5b0d61fdd@mail.gmail.com> (raw)
In-Reply-To: <1231543199.5317.63.camel@dax.rpnet.com>
On Fri, Jan 9, 2009 at 4:19 PM, Richard Purdie <rpurdie@rpsys.net> wrote:
> On Fri, 2009-01-09 at 12:37 -0800, Trent Piepho wrote:
>> On Fri, 9 Jan 2009, Richard Purdie wrote:
>> > for the LED tree updates for 2.6.29. This includes some new drivers,
>> > bugfixes and a core improvement resulting in nicer code.
>> >
>>
>> Any chance of these patches getting accepted? They've been going back and
>> forth for months now.
>>
>> [v2,1/4] leds: Support OpenFirmware led bindings
>> http://patchwork.ozlabs.org/patch/13581/
>>
>> [v2,2/4] leds: Add option to have GPIO LEDs start on
>> http://patchwork.ozlabs.org/patch/13580/
>>
>> [v2,3/4] leds: Let GPIO LEDs keep their current state
>> http://patchwork.ozlabs.org/patch/13583/
>>
>> [v2,4/4] leds: Use tristate property in platform data
>> http://patchwork.ozlabs.org/patch/13584/
>
> I think there was some confusion as to who was going to take them. Are
> the PPC people happy with them? If so I'll merge through the LED tree.
> There are these and a couple of other patches around which have got lost
> in the system. If there is time which I'm hoping there might be, I'll
> try and get a second LED tree merge in.
I'm cool with them going in from the ppc side.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-01-11 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 11:23 Richard Purdie
2009-01-09 20:37 ` Trent Piepho
2009-01-09 23:19 ` Richard Purdie
2009-01-10 12:31 ` Trent Piepho
2009-01-11 0:33 ` Richard Purdie
2009-01-11 1:20 ` Guennadi Liakhovetski
2009-01-11 5:43 ` Trent Piepho
2009-01-11 11:49 ` Richard Purdie
2009-01-11 12:58 ` Trent Piepho
2009-01-11 13:39 ` Richard Purdie
2009-01-11 0:33 ` Grant Likely [this message]
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=fa686aa40901101633r71a143cam21e954d5b0d61fdd@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=akpm@linux-foundation.org \
--cc=lg@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=torvalds@linux-foundation.org \
--cc=xyzzy@speakeasy.org \
/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
all inboxes | Powered by JetHome®