From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, slp@redhat.com,
marcandre.lureau@redhat.com, stefanha@redhat.com,
mathieu.poirier@linaro.org, viresh.kumar@linaro.org,
sgarzare@redhat.com
Subject: Re: [PATCH for 7.2-rc3 v3 0/7] fix vhost-user issues with CI
Date: Wed, 30 Nov 2022 01:57:58 -0500 [thread overview]
Message-ID: <20221130015526-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221128164105.1191058-1-alex.bennee@linaro.org>
Patch 1 is good but inappropriate for 7.2
Patch 2 should be last in series.
Patch 4 we are dropping.
I thought hard about it, I think we should patch vhost user net too
because of the risk introduced by patch 2 (which affects everyone).
Can be a patch on top though.
Besides this, for series:
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
--
MST
prev parent reply other threads:[~2022-11-30 6:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 16:40 [PATCH for 7.2-rc3 v3 0/7] fix vhost-user issues with CI Alex Bennée
2022-11-28 16:40 ` [PATCH v3 1/7] include/hw: attempt to document VirtIO feature variables Alex Bennée
2022-11-29 8:54 ` Stefano Garzarella
2022-11-28 16:41 ` [PATCH v3 2/7] include/hw: VM state takes precedence in virtio_device_should_start Alex Bennée
2022-11-28 17:09 ` Michael S. Tsirkin
2022-11-28 16:41 ` [PATCH v3 3/7] tests/qtests: override "force-legacy" for gpio virtio-mmio tests Alex Bennée
2022-11-28 16:41 ` [PATCH v3 4/7] hw/virtio: ensure a valid host_feature set for virtio-user-gpio Alex Bennée
2022-11-28 18:39 ` Stefan Hajnoczi
2022-11-28 19:39 ` Alex Bennée
2022-11-29 15:48 ` Michael S. Tsirkin
2022-11-29 21:01 ` Stefan Hajnoczi
2022-11-29 21:13 ` Michael S. Tsirkin
2022-11-29 22:53 ` Alex Bennée
2022-11-28 16:41 ` [Virtio-fs] [PATCH v3 5/7] vhost: enable vrings in vhost_dev_start() for vhost-user devices Alex Bennée
2022-11-28 16:41 ` Alex Bennée
2022-11-28 16:41 ` [PATCH v3 6/7] hw/virtio: add started_vu status field to vhost-user-gpio Alex Bennée
2022-11-28 16:41 ` [PATCH v3 7/7] hw/virtio: generalise CHR_EVENT_CLOSED handling Alex Bennée
2022-11-29 5:18 ` Raphael Norwitz
2022-11-29 5:30 ` Michael S. Tsirkin
2022-11-29 14:24 ` Raphael Norwitz
2022-11-30 10:25 ` Alex Bennée
2022-11-30 10:28 ` Michael S. Tsirkin
2022-11-30 11:28 ` Alex Bennée
2022-11-30 6:57 ` Michael S. Tsirkin [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=20221130015526-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=mathieu.poirier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.com \
--cc=stefanha@redhat.com \
--cc=viresh.kumar@linaro.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.