qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Jay Zhou <jianjay.zhou@huawei.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com,
	wangxinxin.wang@huawei.com, weidong.huang@huawei.com,
	quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] docs/devel/migration.txt: keep functions consistent with the code
Date: Fri, 24 Nov 2017 09:46:36 +0000	[thread overview]
Message-ID: <20171124094635.GA2302@work-vm> (raw)
In-Reply-To: <5A177041.7080001@huawei.com>

* Jay Zhou (jianjay.zhou@huawei.com) wrote:
> This patch does not touch any code at all.
> 
> So I think this patch is not relevant to this test failure.

Yes, that's true; there's a block problem that's been affecting all
tests recently.

Dave

> Regards,
> Jay
> 
> On 2017/11/23 17:15, no-reply@patchew.org wrote:
> > Hi,
> > 
> > This series failed automatic build test. Please find the testing commands and
> > their output below. If you have docker installed, you can probably reproduce it
> > locally.
> > 
> > Subject: [Qemu-devel] [PATCH] docs/devel/migration.txt: keep functions consistent with the code
> > Type: series
> > Message-id: 1511426872-13980-1-git-send-email-jianjay.zhou@huawei.com
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2017-11-24  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23  8:47 [Qemu-devel] [PATCH] docs/devel/migration.txt: keep functions consistent with the code Jay Zhou
2017-11-23  9:15 ` no-reply
2017-11-24  1:05   ` Jay Zhou
2017-11-24  9:46     ` Dr. David Alan Gilbert [this message]
2017-12-05  2:18 ` Jay Zhou
2017-12-05 19:58 ` Dr. David Alan Gilbert
2017-12-15 12:21   ` Daniel P. Berrange
2017-12-15 15:15     ` Dr. David Alan Gilbert
2017-12-18  1:36       ` Zhoujian (jay)

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=20171124094635.GA2302@work-vm \
    --to=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.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).