From: Gonglei <arei.gonglei@huawei.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Subo (A)" <subo7@huawei.com>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/5] vhost-scsi: support to assign boot order
Date: Thu, 5 Feb 2015 20:31:06 +0800 [thread overview]
Message-ID: <54D3628A.8000209@huawei.com> (raw)
In-Reply-To: <20150205120432.GA30113@redhat.com>
On 2015/2/5 20:04, Michael S. Tsirkin wrote:
> On Thu, Feb 05, 2015 at 12:10:04PM +0100, Paolo Bonzini wrote:
>>
>>
>> On 05/02/2015 09:51, Gonglei wrote:
>>> Hi, Paolo and Michael
>>>
>>> Which tree does this series can be applied, vhost tree or scsi tree? Thanks.
>>
>> I can apply it to the scsi tree.
>>
>> Paolo
>
> Works for me
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
Thank you. :)
Regards,
-Gonglei
prev parent reply other threads:[~2015-02-05 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 7:08 [Qemu-devel] [PATCH v2 0/5] vhost-scsi: support to assign boot order arei.gonglei
2015-01-29 7:08 ` [Qemu-devel] [PATCH v2 1/5] qdev: support to get a device firmware path directly arei.gonglei
2015-01-29 7:08 ` [Qemu-devel] [PATCH v2 2/5] vhost-scsi: add bootindex property arei.gonglei
2015-01-29 7:08 ` [Qemu-devel] [PATCH v2 3/5] vhost-scsi: realize the TYPE_FW_PATH_PROVIDER interface arei.gonglei
2015-01-29 7:08 ` [Qemu-devel] [PATCH v2 4/5] vhost-scsi: add a property for booting arei.gonglei
2015-01-29 7:08 ` [Qemu-devel] [PATCH v2 5/5] vhost-scsi: set the bootable value of channel/target/lun arei.gonglei
2015-02-03 8:55 ` [Qemu-devel] [PATCH v2 0/5] vhost-scsi: support to assign boot order Gonglei
2015-02-03 11:11 ` Paolo Bonzini
2015-02-03 11:27 ` Gonglei
2015-02-05 8:51 ` Gonglei
2015-02-05 11:10 ` Paolo Bonzini
2015-02-05 12:04 ` Michael S. Tsirkin
2015-02-05 12:31 ` Gonglei [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=54D3628A.8000209@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=subo7@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 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.