xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@novell.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxc: use correct macro when unmapping memory after save operation
Date: Tue, 24 May 2011 08:25:53 -0600	[thread overview]
Message-ID: <4DDBBFF1.4050905@novell.com> (raw)
In-Reply-To: <19931.47489.431098.743040@mariner.uk.xensource.com>

Ian Jackson wrote:
> Jim Fehlig writes ("[Xen-devel] [PATCH] libxc: use correct macro when unmapping memory after save operation"):
>   
>> With some help from Olaf, I've finally got to the bottom of an issue I
>> came across while trying to implement save/restore in the libvirt
>> libxenlight driver.  After issuing the save operation, the saved domain
>> was not being cleaned up properly and left in this state from xl's
>> perspective
>>     
>
> Good catch, thanks.  I have applied this.
>
> Next time, though, can you please be sure to add a Signed-off-by line,
>   

Yes, apologies for the oversight.

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?

Regards,
Jim

  reply	other threads:[~2011-05-24 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 22:04 [PATCH] libxc: use correct macro when unmapping memory after save operation Jim Fehlig
2011-05-23  9:16 ` Ian Campbell
2011-05-24 13:50   ` Ian Jackson
2011-05-24 13:58 ` Ian Jackson
2011-05-24 14:25   ` Jim Fehlig [this message]
2011-05-24 15:52     ` Keir Fraser
2011-05-24 16:18       ` Ian Jackson
2011-05-24 16:02     ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DDBBFF1.4050905@novell.com \
    --to=jfehlig@novell.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).