From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH 2/5] Xl interface change plus changes to code it impacts Date: Tue, 8 Feb 2011 14:41:14 +0000 Message-ID: <1297176074.9388.116.camel@zakaz.uk.xensource.com> References: <4D50628A.2000307@gmail.com> <1297175897.9388.114.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1297175897.9388.114.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Kamala Narasimhan Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tue, 2011-02-08 at 14:38 +0000, Ian Campbell wrote: > On Mon, 2011-02-07 at 21:22 +0000, Kamala Narasimhan wrote: > > Attached are the changes made to xl disk related interface per earlier discussion. Please let me know if there are further comments/issues to fix. > > Please can you include a full/standalone commit message describing the > change and the reasons for it etc, The reference to "earlier discussion" > is likely to be lost with time. > > Did we decide to leave DISK_BACKEND_DEFAULT (i.e. libxl chooses based on > the image type, host's backend support etc) for 4.2? I don't mind if we > did but does that make "block-dev-type" as described in patch 1/5 > non-optional? (and therefore not really deprecated) Maybe this is handled in xl by patch 3/5? (I should really apply the patch and read the result instead of trying to decode the meaning from the patch form) Ian.