From: Trent Piepho <xyzzy@speakeasy.org>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Guennadi Liakhovetski <lg@denx.de>,
linuxppc-dev@ozlabs.org
Subject: Re: [GIT PULL] LED updates for 2.6.29
Date: Sat, 10 Jan 2009 04:31:06 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0901100428230.1626@shell2.speakeasy.net> (raw)
In-Reply-To: <1231543199.5317.63.camel@dax.rpnet.com>
On Fri, 9 Jan 2009, Richard Purdie 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.
The LED tree makes more sense for what's left I think. There was a
openfirmware gpio patch, but that's already gone in. What's left only
touches led files and the device tree binding docs.
AFAIK, there were no objections to the patches left.
WARNING: multiple messages have this Message-ID (diff)
From: Trent Piepho <xyzzy@speakeasy.org>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
Guennadi Liakhovetski <lg@denx.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] LED updates for 2.6.29
Date: Sat, 10 Jan 2009 04:31:06 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0901100428230.1626@shell2.speakeasy.net> (raw)
In-Reply-To: <1231543199.5317.63.camel@dax.rpnet.com>
On Fri, 9 Jan 2009, Richard Purdie 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.
The LED tree makes more sense for what's left I think. There was a
openfirmware gpio patch, but that's already gone in. What's left only
touches led files and the device tree binding docs.
AFAIK, there were no objections to the patches left.
next prev parent reply other threads:[~2009-01-10 12:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 11:23 [GIT PULL] LED updates for 2.6.29 Richard Purdie
2009-01-09 20:37 ` Trent Piepho
2009-01-09 23:19 ` Richard Purdie
2009-01-10 12:31 ` Trent Piepho [this message]
2009-01-10 12:31 ` Trent Piepho
2009-01-11 0:33 ` Richard Purdie
2009-01-11 0:33 ` Richard Purdie
2009-01-11 1:20 ` Guennadi Liakhovetski
2009-01-11 1:20 ` Guennadi Liakhovetski
2009-01-11 5:43 ` Trent Piepho
2009-01-11 5:43 ` Trent Piepho
2009-01-11 11:49 ` Richard Purdie
2009-01-11 11:49 ` Richard Purdie
2009-01-11 12:58 ` Trent Piepho
2009-01-11 12:58 ` Trent Piepho
2009-01-11 13:39 ` Richard Purdie
2009-01-11 13:39 ` Richard Purdie
2009-01-11 0:33 ` Grant Likely
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=Pine.LNX.4.58.0901100428230.1626@shell2.speakeasy.net \
--to=xyzzy@speakeasy.org \
--cc=akpm@linux-foundation.org \
--cc=lg@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rpurdie@rpsys.net \
--cc=torvalds@linux-foundation.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 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.