From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932231Ab0KVUVT (ORCPT ); Mon, 22 Nov 2010 15:21:19 -0500 Received: from claw.goop.org ([74.207.240.146]:43901 "EHLO claw.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932102Ab0KVUVS (ORCPT ); Mon, 22 Nov 2010 15:21:18 -0500 Message-ID: <4CEAD0BC.9020407@goop.org> Date: Mon, 22 Nov 2010 12:21:16 -0800 From: Jeremy Fitzhardinge User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101027 Fedora/3.1.6-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.6 MIME-Version: 1.0 To: Jens Axboe CC: Stephen Rothwell , Xen Devel , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Christoph Hellwig Subject: Re: linux-next: manual merge of the xen tree with Linus' tree References: <20101115112352.6cbf5604.sfr@canb.auug.org.au> <4CE1A07B.5010202@goop.org> <4CE1A124.3010108@kernel.dk> <4CEACF49.8040701@goop.org> <4CEACFBC.8050402@kernel.dk> In-Reply-To: <4CEACFBC.8050402@kernel.dk> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/22/2010 12:17 PM, Jens Axboe wrote: > I'll drop that because you should be seeing those changes come via Jens. >>> Yep, since Linus pulled the last batch, for-linus now has the next bits >>> (which include the xen barrier set). >> These don't seem to be in -rc3. Did they get dropped on the ground >> somewhere? > No, they are in for-linus as written above. Just not shipped off yet, > will be soon. No problem, I was just following up on everything outstanding for upstream. Thanks, J