All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl/remus: fix the return value of the checkpoint callback
Date: Thu, 16 Jul 2015 10:45:14 +0800	[thread overview]
Message-ID: <55A71ABA.6070008@cn.fujitsu.com> (raw)
In-Reply-To: <21926.25110.109866.876891@mariner.uk.xensource.com>



On 07/15/2015 09:37 PM, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH] libxl/remus: fix the return value of the checkpoint callback"):
>> Does that mean it won't apply to current staging?
>
> Indeed it doesn't.
>
>> I think we probably want this fix ASAP rather than waiting for that
>> series?
>
> Yes.  Patch just sent.  Untested but fairly obvious.  Yang, do you
> want to test this, or do you want us to apply it as-is ?  I don't have
> a remus test setup.

Please apply, thanks!

>
> This is the second rc-handling bug in 31c836f4 "libxl: events: Permit
> timeouts to signal ao abort".  I am going to re-read that patch to see
> if I can find any more.
>
> Ian.
> .
>

-- 
Thanks,
Yang.

      reply	other threads:[~2015-07-16  2:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 10:32 [PATCH] libxl/remus: fix the return value of the checkpoint callback Yang Hongyang
2015-07-15 12:13 ` Ian Campbell
2015-07-15 12:30   ` Yang Hongyang
2015-07-15 13:35   ` [PATCH] libxl: events: Do not abort remus with ERROR_TIMEOUT Ian Jackson
2015-07-15 13:45     ` Ian Campbell
2015-07-15 13:47     ` Wei Liu
2015-07-16  2:44     ` Yang Hongyang
2015-07-16 15:51       ` Ian Campbell
2015-07-15 13:37   ` [PATCH] libxl/remus: fix the return value of the checkpoint callback Ian Jackson
2015-07-16  2:45     ` Yang Hongyang [this message]

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=55A71ABA.6070008@cn.fujitsu.com \
    --to=yanghy@cn.fujitsu.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.