From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: powerpc -next branch
Date: Mon, 01 Feb 2010 16:43:30 +1100 [thread overview]
Message-ID: <1265003010.8287.34.camel@pasglop> (raw)
So I'm about to do a proper -next branch for the next round (it's about
time !). I'll probably push a handful or two of things in my 'test'
branch tonight, which are then going to hit -next in a day or two if
nobody complains.
There's more to pickup though.
However, the bulk of the stuff pending on patchwork this time around
seems to be freescale related and thus will go through Kumar or Grant
for 52xx related bits.
Kumar, when do you expect to have a -next for me ?
Cheers,
Ben.
reply other threads:[~2010-02-01 5:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1265003010.8287.34.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).