From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: next branch update
Date: Thu, 11 Jun 2009 11:30:07 +1000 [thread overview]
Message-ID: <1244683807.5739.28.camel@pasglop> (raw)
In-Reply-To: <20090610210923.2323202f@lappy.seanm.ca>
On Wed, 2009-06-10 at 21:09 -0400, Sean MacLennan wrote:
> I was expecting an rc9 and another week. Probably others where caught
> off guard. Patch below.
>
Note that this simple patch qualifies as a bug fix in my book and thus
is less constrainted. I would happily have merged it in -rc4 :-)
Cheers,
Ben.
next prev parent reply other threads:[~2009-06-11 1:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 7:26 next branch update Benjamin Herrenschmidt
2009-05-21 8:06 ` Stephen Rothwell
2009-06-10 21:56 ` Sean MacLennan
2009-06-11 0:50 ` Benjamin Herrenschmidt
2009-06-11 1:09 ` Sean MacLennan
2009-06-11 1:30 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-11 5:02 Benjamin Herrenschmidt
2008-12-02 15:11 Kumar Gala
2008-12-03 11:34 ` Paul Mackerras
2008-12-03 15:39 ` Kumar Gala
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=1244683807.5739.28.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.com \
/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).