From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH for 7.1 v1 0/5] virtio fixes (split from virtio-gpio series)
Date: Wed, 27 Jul 2022 16:56:48 +0100 [thread overview]
Message-ID: <20220727155653.3974426-1-alex.bennee@linaro.org> (raw)
Hi,
This is just a split out series based on:
Subject: [PATCH v3 for 7.2 00/21] virtio-gpio and various virtio cleanups
Date: Tue, 26 Jul 2022 20:21:29 +0100
Message-Id: <20220726192150.2435175-1-alex.bennee@linaro.org>
with the patches identified by mst:
Right. Still I think some are fixes we should merge now.
I am thinking patches 5, 7,8,9 ? 6 if it makes backporting
much easier. WDYT? If you agree pls separate bugfixes in
series I can apply. Thanks!
So here they are ;-)
Alex Bennée (5):
block/vhost-user-blk-server: don't expose
VHOST_USER_F_PROTOCOL_FEATURES
hw/virtio: incorporate backend features in features
hw/virtio: gracefully handle unset vhost_dev vdev
hw/virtio: handle un-configured shutdown in virtio-pci
hw/virtio: fix vhost_user_read tracepoint
block/export/vhost-user-blk-server.c | 3 +--
hw/virtio/vhost-user.c | 13 ++++++++++---
hw/virtio/vhost.c | 10 +++++++---
hw/virtio/virtio-pci.c | 9 +++++++--
4 files changed, 25 insertions(+), 10 deletions(-)
--
2.30.2
next reply other threads:[~2022-07-27 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:56 Alex Bennée [this message]
2022-07-27 15:56 ` [PATCH v1 1/5] block/vhost-user-blk-server: don't expose VHOST_USER_F_PROTOCOL_FEATURES Alex Bennée
2022-07-28 8:46 ` Kevin Wolf
2022-07-28 10:27 ` Alex Bennée
2022-07-27 15:56 ` [PATCH v1 2/5] hw/virtio: incorporate backend features in features Alex Bennée
2022-07-27 15:56 ` [PATCH v1 3/5] hw/virtio: gracefully handle unset vhost_dev vdev Alex Bennée
2022-07-27 15:56 ` [PATCH v1 4/5] hw/virtio: handle un-configured shutdown in virtio-pci Alex Bennée
2022-07-27 15:56 ` [PATCH v1 5/5] hw/virtio: fix vhost_user_read tracepoint Alex Bennée
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=20220727155653.3974426-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--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).