[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1231543199.5317.63.camel@dax.rpnet.com>
Date: Fri, 09 Jan 2009 23:19:59 +0000
From: Richard Purdie <rpurdie@...ys.net>
To: Trent Piepho <xyzzy@...akeasy.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Guennadi Liakhovetski <lg@...x.de>
Subject: Re: [GIT PULL] LED updates for 2.6.29
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.
Richard
--
Richard Purdie
Intel Open Source Technology Centre
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists