From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for January 31
Date: Mon, 31 Jan 2011 10:25:34 -0800 [thread overview]
Message-ID: <4D46FE9E.3010502@goop.org> (raw)
In-Reply-To: <20110131170506.GA11939@dumpdata.com>
On 01/31/2011 09:05 AM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 31, 2011 at 05:41:13PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20110121:
>>
>> New tree: unicore32
>>
>> Renamed tree: swiotlb-xen to xen-two
> Sweet. Thank you.
>> Dropped tree: xen
> Uh, why? Jeremy's tree should be OK now? Did something not
> compile correctly?
No, keep it dropped for now. I'll do a proper linux-next branch shortly.
J
next prev parent reply other threads:[~2011-01-31 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 6:41 linux-next: Tree for January 31 Stephen Rothwell
2011-01-31 17:05 ` Konrad Rzeszutek Wilk
2011-01-31 18:25 ` Jeremy Fitzhardinge [this message]
2011-01-31 18:18 ` linux-next: Tree for January 31 (ip_vs) Randy Dunlap
2011-01-31 21:18 ` Simon Horman
2011-01-31 22:57 ` Simon Horman
2011-01-31 23:00 ` David Miller
2011-02-01 0:03 ` Simon Horman
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=4D46FE9E.3010502@goop.org \
--to=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.