All of lore.kernel.org
 help / color / mirror / Atom feed
From: <peng.hao2@zte.com.cn>
To: <ehabkost@redhat.com>
Cc: zhong.weidong@zte.com.cn, kvm@vger.kernel.org,
	rkrcmar@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
	pbonzini@redhat.com
Subject: Re: [PATCH V5 1/4] target-i386: introduce coalesced_pio kvm headerupdate
Date: Fri, 31 Aug 2018 08:14:13 +0800 (CST)	[thread overview]
Message-ID: <201808310814138091604@zte.com.cn> (raw)

>On Thu, Aug 30, 2018 at 11:50:13PM +0800, Peng Hao wrote:
>> add coalesced_pio's struct and KVM_CAP_COALESCED_PIO header.
>> 
>> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
>> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

>I think there was a misunderstanding. I never sent a Reviewed-by
>line for this patch, because we need to get the KVM patch
>accepted before including this.
I'm sorry very much. I saw the e-mail from you:
          "On Sat, Aug 25, 2018 at 08:19:48PM +0800, Peng Hao wrote:
           > Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>

          Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>"
So I misunderstatnd you add "reviewed-by" for the series patches. 
I will resend these patches to correct my mistake.
>-- 
>Eduardo

WARNING: multiple messages have this Message-ID (diff)
From: <peng.hao2@zte.com.cn>
To: ehabkost@redhat.com
Cc: pbonzini@redhat.com, mst@redhat.com, rkrcmar@redhat.com,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	zhong.weidong@zte.com.cn
Subject: Re: [Qemu-devel] [PATCH V5 1/4] target-i386: introduce coalesced_pio kvm headerupdate
Date: Fri, 31 Aug 2018 08:14:13 +0800 (CST)	[thread overview]
Message-ID: <201808310814138091604@zte.com.cn> (raw)

>On Thu, Aug 30, 2018 at 11:50:13PM +0800, Peng Hao wrote:
>> add coalesced_pio's struct and KVM_CAP_COALESCED_PIO header.
>> 
>> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
>> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

>I think there was a misunderstanding. I never sent a Reviewed-by
>line for this patch, because we need to get the KVM patch
>accepted before including this.
I'm sorry very much. I saw the e-mail from you:
          "On Sat, Aug 25, 2018 at 08:19:48PM +0800, Peng Hao wrote:
           > Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>

          Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>"
So I misunderstatnd you add "reviewed-by" for the series patches. 
I will resend these patches to correct my mistake.
>-- 
>Eduardo

             reply	other threads:[~2018-08-31  0:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  0:14 peng.hao2 [this message]
2018-08-31  0:14 ` [Qemu-devel] [PATCH V5 1/4] target-i386: introduce coalesced_pio kvm headerupdate peng.hao2
  -- strict thread matches above, loose matches on Subject: below --
2018-09-07 21:02 [PATCH V5 1/4] target-i386: introduce coalesced_pio kvm header update Michael S. Tsirkin
2018-10-17  1:37 ` [PATCH V5 1/4] target-i386: introduce coalesced_pio kvm headerupdate peng.hao2

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=201808310814138091604@zte.com.cn \
    --to=peng.hao2@zte.com.cn \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.com \
    --cc=zhong.weidong@zte.com.cn \
    /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.