Re: [Xen-devel] [PATCH] libxc: use correct macro when unmapping

Keir Fraser writes ("Re: [Xen-devel] [PATCH] libxc: use correct macro when 
unmapping memory after save operation"):
> On 24/05/2011 15:25, "Jim Fehlig" <jfehlig@xxxxxxxxxx> wrote:
> > 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?
> 
> Worth pointing out that at the moment only I seem to be backporting to the
> stable trees, and I only do that for tools patches that I am explicitly
> requested to do by a toolstack maintainer. A comment in a changeset comment
> is fine if it is a reminder for Ian, but it is useless in terms of getting
> me to apply it to 4.1-testing (for example).

Indeed.  It is a reminder for me.

Ian.

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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

RE: [Xen-devel] Xen security advisory CVE-2011-1898 - VT-d (PCI passthrough) MSI, Ian Pratt

Next by Date:

[Xen-devel] Re: Xen MMU's requirement to pin pages RO and initial_memory_mapping., Stefano Stabellini

Previous by Thread:

Re: [Xen-devel] [PATCH] libxc: use correct macro when unmapping memory after save operation, Keir Fraser

Next by Thread:

Re: [Xen-devel] [PATCH] libxc: use correct macro when unmapping memory after save operation, Ian Jackson

Indexes:

[Date] [Thread] [Top] [All Lists]

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] [PATCH] libxc: use correct macro when unmapping memory a