This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: linux-next: manual merge of the xen tree with the ti

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: linux-next: manual merge of the xen tree with the tip tree
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Fri, 22 Oct 2010 22:32:02 +0100
Cc: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>, Devel <Xen-devel@xxxxxxxxxxxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Yinghai Lu <yinghai@xxxxxxxxxx>, Xen, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-next@xxxxxxxxxxxxxxx" <linux-next@xxxxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Gianluca Guida <gianluca.guida@xxxxxxxxxx>
Delivery-date: Fri, 22 Oct 2010 14:33:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CC1DA58.8000606@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101022140335.c4a3a48f.sfr@xxxxxxxxxxxxxxxx> <20101022080129.GA8474@xxxxxxx> <4CC1DA58.8000606@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Fri, 22 Oct 2010, Jeremy Fitzhardinge wrote:
> > Crap like that is just _NOT_ acceptable, and you know that perfectly well - 
> > if you 
> > do this to arch/x86/ i'll be forced to ask for the Xen tree to be removed 
> > from 
> > linux-next and be done via the x86 tree again.
> Hey, hey, hold your horses.  This is a wildly obsolete patch that we
> were discussing a few weeks ago, but Yinghai did a proper alternative
> for the memblock universe.
> It was never in linux-next, and never intended to be.  I'm not sure why
> it has appeared in linux-next now; it isn't in my branch.  I wonder if
> it appeared in another Xen-related branch.  Let me investigate.

I think I merged in my tree a snapshot of Jeremy's upstream/xen that
apparently was not meant for upstream at all.
And I did that just to solve a trivial 5 lines conflict because my patch
series don't actually depend on any of Jeremy's patches.

I solved the problem taking the radical approach: I removed the
merge with upstream/xen altogether and also removed the commit that
conflicts with one of Jeremy's commits.
There shouldn't be any more conflicts now, and surely there shouldn't be
any more unwanted old commits.

I apologize for any problems caused but none of this was intentional.

Xen-devel mailing list