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 v2 0/4] virtio fixes (split from virtio-gpio series)
Date: Thu, 28 Jul 2022 14:54:59 +0100 [thread overview]
Message-ID: <20220728135503.1060062-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!
but I've dropped the first patch as that was actually a backend and
I've added one of Jason's acked-bys.
Alex Bennée (4):
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
hw/virtio/vhost-user.c | 13 ++++++++++---
hw/virtio/vhost.c | 10 +++++++---
hw/virtio/virtio-pci.c | 9 +++++++--
3 files changed, 24 insertions(+), 8 deletions(-)
--
2.30.2
next reply other threads:[~2022-07-28 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 13:54 Alex Bennée [this message]
2022-07-28 13:55 ` [PATCH v2 1/4] hw/virtio: incorporate backend features in features Alex Bennée
2022-08-17 11:00 ` Michael S. Tsirkin
2022-10-26 6:11 ` Yajun Wu
2022-10-26 7:41 ` Alex Bennée
2022-11-10 10:35 ` Yajun Wu
2022-07-28 13:55 ` [PATCH v2 2/4] hw/virtio: gracefully handle unset vhost_dev vdev Alex Bennée
2022-08-17 11:01 ` Michael S. Tsirkin
2022-08-18 6:35 ` Alex Bennée
2022-07-28 13:55 ` [PATCH v2 3/4] hw/virtio: handle un-configured shutdown in virtio-pci Alex Bennée
2022-07-28 13:55 ` [PATCH v2 4/4] 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=20220728135503.1060062-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 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.