WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates

To: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 00 of 10] blkfront pvops updates
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 29 Apr 2010 14:10:52 -0700
Cc: ksrinivasan <ksrinivasan@xxxxxxxxxx>, Xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Thu, 29 Apr 2010 14:11:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1272574715.25447.34.camel@xxxxxxxxxxxxxxxxxxxxxxx>
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: <patchbomb.1272507577@xxxxxxxxxxxxxxxxxxxxxxx> <4BD9E2EE.5060402@xxxxxxxx> <1272571912.25447.11.camel@xxxxxxxxxxxxxxxxxxxxxxx> <1272574715.25447.34.camel@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
On 04/29/2010 01:58 PM, Daniel Stodden wrote:
> Ah, that's where the previous stuff ended up. I thought those probably
> just got dropped.
>   

I thought the changes in these patches looked somewhat familiar.

> Let's just scratch those. It's been months, so if they didn't make it
> back then, they won't need to complicate stuff now either.
>
> So I should probably merge with xen/frontend. If those matter, they must
> be on some branch which matters. Which one is it? I thought the one
> which matters is xen/master? Is it xen/next?
>   

The flow of changes is (ideally):

    <topic branch> -> xen/next -> xen/stable*

where "->" is merged into.

I'm going to clean things up a bit by re-creating xen/blkfront with the
changes from xen/frontend.  If you rebase your patches onto xen/frontend
then I should be able to easily incorporate them into that cleanup.

Sorry for the mixup.

Thanks,
    J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>