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] libxc: use correct macro when unmapping memory a

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] libxc: use correct macro when unmapping memory after save operation
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 24 May 2011 17:02:36 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 24 May 2011 09:16:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DDBBFF1.4050905@xxxxxxxxxx>
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: <4DD6E579.7060304@xxxxxxxxxx> <19931.47489.431098.743040@xxxxxxxxxxxxxxxxxxxxxxxx> <4DDBBFF1.4050905@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Jim Fehlig writes ("Re: [Xen-devel] [PATCH] libxc: use correct macro when 
unmapping memory after save operation"):
> BTW, thanks for the commit message note about "backporting to relevant
> earlier trees".  I was going to ask that this be applied to
> 4.1-testing.  Should such a statement be included for fixes that apply
> to multiple trees?  Is it helpful for scanning potential backports in
> -unstable?

Yes, exactly.  I think it would be a good idea to put such a statement
(including at least the literal string "backport" in such changes).

That's why I put it in in that case.  We're about to do RCs point
releases for 4.0 and 4.1 but after that we should consider these
changes.

Ian.

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