[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Jim Fehlig <jfehlig@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Tue, 24 May 2011 16:52:03 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 24 May 2011 09:01:47 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=xL3QQDXivc/6pGcNS37CQTEu3Z/ru6jzLXyNW0B9m7d98pkluGOIo8RpCM3btIksd/ uG5dWXSaKUktRawm4t0Y4mMGEeegKgfq/fcrb0gERB4CW3uvTUHI16UsmgtGQgvZVR2j ximGLq5ELWAR2yUpesNB3T4Y6YVvoJir22JIk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcwaKoY9PpOmPUjDT0ycwMwK7h0/Cg==
  • Thread-topic: [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).

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.