From: Stefan Hajnoczi <stefanha@redhat.com>
To: Coiby Xu <coiby.xu@gmail.com>
Cc: kwolf@redhat.com, bharatlkmlkvm@gmail.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v8 0/4] vhost-user block device backend implementation
Date: Thu, 11 Jun 2020 16:27:44 +0100 [thread overview]
Message-ID: <20200611152744.GD77457@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200604233538.256325-1-coiby.xu@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
On Fri, Jun 05, 2020 at 07:35:34AM +0800, Coiby Xu wrote:
> v8
> - re-try connecting to socket server to fix asan error
> - fix license naming issue
Great, thanks for posting these patches!
I have posted feedback. I'd like to merge this soon. If you are busy I
can send you patches that address the comments I've made, please let me
know.
Thanks,
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-11 15:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 23:35 [PATCH v8 0/4] vhost-user block device backend implementation Coiby Xu
2020-06-04 23:35 ` [PATCH v8 1/4] Allow vu_message_read to be replaced Coiby Xu
2020-06-11 10:45 ` Stefan Hajnoczi
2020-06-11 11:26 ` Marc-André Lureau
2020-06-04 23:35 ` [PATCH v8 2/4] generic vhost user server Coiby Xu
2020-06-11 13:14 ` Stefan Hajnoczi
2020-06-14 18:43 ` Coiby Xu
2020-06-04 23:35 ` [PATCH v8 3/4] vhost-user block device backend server Coiby Xu
2020-06-11 15:24 ` Stefan Hajnoczi
2020-06-14 19:04 ` Coiby Xu
2020-06-04 23:35 ` [PATCH v8 4/4] new qTest case to test the vhost-user-blk-server Coiby Xu
2020-06-05 5:01 ` Thomas Huth
2020-06-05 6:22 ` Coiby Xu
2020-06-05 9:25 ` Thomas Huth
2020-06-05 13:27 ` Coiby Xu
2020-06-11 12:37 ` [PATCH v8 0/4] vhost-user block device backend implementation Stefano Garzarella
2020-06-14 18:46 ` Coiby Xu
2020-06-15 8:46 ` Stefano Garzarella
2020-06-16 6:55 ` Coiby Xu
2020-06-11 15:27 ` Stefan Hajnoczi [this message]
2020-06-12 15:58 ` Coiby Xu
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=20200611152744.GD77457@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=bharatlkmlkvm@gmail.com \
--cc=coiby.xu@gmail.com \
--cc=kwolf@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 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).