From: Andrew Morton <akpm@linux-foundation.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
David Brownell <dbrownell@users.sourceforge.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: 2.6.33 -next tree
Date: Tue, 8 Dec 2009 14:45:05 -0800 [thread overview]
Message-ID: <20091208144505.af1dd7a3.akpm@linux-foundation.org> (raw)
In-Reply-To: <1260311383.16132.4.camel@pasglop>
On Wed, 09 Dec 2009 09:29:43 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Tue, 2009-12-08 at 14:33 -0700, Grant Likely wrote:
> >
> > Are you able to pull this tree, or should I ask Linus to pull it
> > directly?
> >
> > It contains mpc5200 and xilinx stuff. Some of it is SPI related, but
> > I'm now the SPI co-maintainer, so I have no problem with it going in
> > via your tree. :-) Regardless, I want to get it out to Linus ASAP.
> >
> > This tree has also been in linux-next for a while now, so it should be
> > a safe pull.
>
> I'll pull it, I'll pull it, stop nagging :-)
>
ooh, does nagging work?
<writes that down somewhere>
next prev parent reply other threads:[~2009-12-08 22:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 6:10 2.6.33 -next tree Grant Likely
2009-11-05 8:02 ` Stephen Rothwell
2009-11-05 8:08 ` Grant Likely
2009-11-05 8:13 ` Stephen Rothwell
2009-12-08 21:33 ` Grant Likely
2009-12-08 21:54 ` Grant Likely
2009-12-08 22:29 ` Benjamin Herrenschmidt
2009-12-08 22:45 ` Andrew Morton [this message]
2009-12-08 22:50 ` Grant Likely
2009-12-09 4:25 ` Olof Johansson
2009-12-09 4:29 ` Benjamin Herrenschmidt
2009-12-09 9:26 ` Luotao Fu
2009-12-09 13:40 ` 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=20091208144505.af1dd7a3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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.