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

Re: [xen-devel][PATCH 2/5] Xl interface change plus changes to code it i

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [xen-devel][PATCH 2/5] Xl interface change plus changes to code it impacts
From: Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>
Date: Tue, 15 Feb 2011 14:38:00 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 15 Feb 2011 11:38:57 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3ZWG/xJnOyQ0QVmGtFINjAPT+qkLCzb/aHoogrl2vlY=; b=ax2MnT2Aaw9aZxN112UzTw96UBs2fskzIhkmh6rzQApV82fbCDRImX635U9GiiHgnv 7soYcYNnq+cY5IDGZf0kAxPR498aFBqVwzmd8cteOKktrf8LSFaFV7DNihucKyWw4d5x 2VaJZwCiVLQPpnhg/Y29pKDU/YEVtdKrlBTxE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=g//HncB/UPMGMwySh7M8oCfig1Eg6WR2OyPiLEzih4I7ltfh6lVWu5hUQl/YVA7IGz 5C0pbiAQwosOKafWG+Ce5K1DFgJOect9getkk/3MubEgiQmNFSF+6ALf/0GetSeHvKwo TDdj0FPFJN6aWlwSpWfcNYJKLJmhbD+xJ1Jm0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19802.53860.260105.696834@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <4D5060EB.3060109@xxxxxxxxx> <4D52DB1E.6080101@xxxxxxxxx> <alpine.DEB.2.00.1102101143110.7277@kaball-desktop> <4D541AC6.6040802@xxxxxxxxx> <4D5443E6.8010704@xxxxxxxxx> <alpine.DEB.2.00.1102111228340.2826@kaball-desktop> <4D555368.3010504@xxxxxxxxx> <4D558A02.6010106@xxxxxxxxx> <19801.27199.25918.814669@xxxxxxxxxxxxxxxxxxxxxxxx> <4D5987C6.4080807@xxxxxxxxx> <19802.53860.260105.696834@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.24 (X11/20101027)
Ian Jackson wrote:
> Kamala Narasimhan writes ("Re: [xen-devel][PATCH 2/5] Xl interface change 
> plus changes to code it impacts"):
>> Attached patch should address your concerns.
> 
> Thanks for this.  However, there were other changes made between
> this most recent version and the previous version, besides the ones
> I mentioned in my comments and which you said you'd address.
> 
> When you post an updated version of a patch you should state
> separately
>  - what the patch does to the tree, including intended changes,
>    motivation, etc., as you have done (for the commit message)
>  - how the patch differs from the previous version, if applicable
> 
> Can you explain what the changes you made and why you made them ?
> Ideally in general you should use revision control system tools to
> make sure that you know what they all are.
> 
> But, for your info here is the output of
>   diff -w --exclude=\*{~,.o,.d,.opic} -ru A B |grep -v '^Only in'
> 
> Most of this is formatting noise, which addresses my comments.
> 
> However, you have also:
>   * Initialised disk->format and disk->backend somewhere you
>     previously didn't
>   * Recognised the "tap2" prefix in a place you previously didn't
>   * Changed the handling of the "aio" and "raw" prefixes
>
Yes, they are all changes made based on input from Stefano and in an attempt to
be in sync with the documentation.  Ideally we wouldn't need these changes if we
were to go with the rest of the patches but since we made a decision not to go
with the rest before 4.2, we decided to do some minimal changes to sync with the
doc.

> Normally patch such as this one, which is presented as being mature,
> ought not to need unexplained semantic changes at this late stage.
I think we are beating to death an already dull set of changes which makes it
all the more uninteresting to me :)  But I digress...

Just to be clear - Would you accept the patch I sent earlier if I extended the
description to include the fact that I initialize disk format, backend to
default values and changed how we handle "aio" prefix plus recognize "raw" and
"tap2" prefixes now?

Kamala



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