From: Johannes Berg <johannes@sipsolutions.net>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com
Subject: Re: [PATCH v5 0/6] small vhost changes and in-band notifications
Date: Thu, 13 Feb 2020 14:26:10 +0100 [thread overview]
Message-ID: <16ac7144ac33d52a740e227e9290a1eb41596e09.camel@sipsolutions.net> (raw)
In-Reply-To: <20200123081708.7817-1-johannes@sipsolutions.net>
On Thu, 2020-01-23 at 09:17 +0100, Johannes Berg wrote:
> Hi,
>
> Here's a repost of all the patches I sent back in August, with the
> in-band notifications rebased over the reset patch, so IDs have now
> changed a bit.
Ping?
The patches still apply on top of latest qemu.
I wanted to send some corresponding kernel patches, but without the
protocol nailed down ...
johannes
next prev parent reply other threads:[~2020-02-13 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 8:17 [PATCH v5 0/6] small vhost changes and in-band notifications Johannes Berg
2020-01-23 8:17 ` [PATCH v5 1/6] libvhost-user: implement VHOST_USER_PROTOCOL_F_REPLY_ACK Johannes Berg
2020-01-23 8:17 ` [PATCH v5 2/6] libvhost-user-glib: fix VugDev main fd cleanup Johannes Berg
2020-01-23 8:17 ` [PATCH v5 3/6] libvhost-user-glib: use g_main_context_get_thread_default() Johannes Berg
2020-01-23 8:17 ` [PATCH v5 4/6] libvhost-user: handle NOFD flag in call/kick/err better Johannes Berg
2020-01-23 8:17 ` [PATCH v5 5/6] docs: vhost-user: add in-band kick/call messages Johannes Berg
2020-01-23 8:17 ` [PATCH v5 6/6] libvhost-user: implement in-band notifications Johannes Berg
2020-02-13 13:26 ` Johannes Berg [this message]
2020-02-13 13:35 ` [PATCH v5 0/6] small vhost changes and " Michael S. Tsirkin
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=16ac7144ac33d52a740e227e9290a1eb41596e09.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=mst@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).