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 21:43:27 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0901102138300.1626@shell2.speakeasy.net> (raw)
In-Reply-To: <1231633983.5330.32.camel@dax.rpnet.com>
On Sun, 11 Jan 2009, Richard Purdie wrote:
> On Sat, 2009-01-10 at 04:31 -0800, Trent Piepho wrote:
> > 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.
>
> Ok, these are now queued in the LED tree:
>
> http://git.o-hand.com/cgit.cgi/linux-rpurdie-leds/log/
>
> I did merge the last three patches in one and make some changes to deal
> with some other outstanding issues. Let me know ASAP if there are any
> problems.
Since the last patch looks like it's just my three patches folded into one,
shouldn't I be listed as the author and the primary signed off by?
next prev parent reply other threads:[~2009-01-11 5:43 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 [this message]
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
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.0901102138300.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 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®