All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Alexey Perevalov <a.perevalov@samsung.com>
Cc: qemu-devel@nongnu.org, i.maximets@samsung.com,
	dgilbert@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [[PATCH V7] 09/11] migration: calculate vCPU blocktime on dst side
Date: Wed, 7 Jun 2017 19:14:23 +0800	[thread overview]
Message-ID: <20170607111423.GC4314@lemon.lan> (raw)
In-Reply-To: <dc236aea-2015-3384-7a18-a67406df0586@samsung.com>

On Wed, 06/07 12:29, Alexey Perevalov wrote:
> On 06/07/2017 12:24 PM, Fam Zheng wrote:
> > On Wed, 06/07 01:40, no-reply@patchew.org wrote:
> > > Hi,
> > > 
> > > This series failed build test on s390x host. Please find the details below.
> > So what happened is the double '[[' in the subject line confused Patchew, and
> > each patch in this series is treated as a standalone patch.
> it's not bad to check every patch in sequence separately,
> but including previous patches )

That won't happen because patchew cannot reason about the dependencies any more
because it doesn't recognized subject tags around this nested [] syntax.

Fam

> 
> > 
> > Fam
> > 
> > 
> > 
> 
> -- 
> Best regards,
> Alexey Perevalov
> 

  reply	other threads:[~2017-06-07 11:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170607073601eucas1p1b1897ed7d52d9edfed31971c592c2300@eucas1p1.samsung.com>
2017-06-07  7:35 ` [Qemu-devel] [[PATCH V7] 00/11] calculate blocktime for postcopy live migration Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 01/11] userfault: add pid into uffd_msg & update UFFD_FEATURE_* Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 02/11] migration: pass MigrationIncomingState* into migration check functions Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 03/11] migration: fix hardcoded function name in error report Alexey Perevalov
2017-06-07  8:10     ` no-reply
2017-06-07  9:29     ` no-reply
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 04/11] migration: split ufd_version_check onto receive/request features part Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 05/11] migration: introduce postcopy-blocktime capability Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 06/11] migration: add postcopy blocktime ctx into MigrationIncomingState Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 07/11] migration: add bitmap for copied page Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 08/11] migration: postcopy_place_page factoring out Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 09/11] migration: calculate vCPU blocktime on dst side Alexey Perevalov
2017-06-07  8:40     ` no-reply
2017-06-07  9:24       ` Fam Zheng
2017-06-07  9:29         ` Alexey Perevalov
2017-06-07 11:14           ` Fam Zheng [this message]
2017-06-07 10:52     ` no-reply
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 10/11] migration: add postcopy total blocktime into query-migrate Alexey Perevalov
2017-06-07  7:35   ` [Qemu-devel] [[PATCH V7] 11/11] migration: postcopy_blocktime documentation Alexey Perevalov

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=20170607111423.GC4314@lemon.lan \
    --to=famz@redhat.com \
    --cc=a.perevalov@samsung.com \
    --cc=dgilbert@redhat.com \
    --cc=i.maximets@samsung.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.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.