From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, fam@euphon.net, berrange@redhat.com,
f4bug@amsat.org, aurelien@aurel32.net, pbonzini@redhat.com,
stefanha@redhat.com, crosa@redhat.com,
"Raphael Norwitz" <raphael.norwitz@nutanix.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"open list:Block layer core" <qemu-block@nongnu.org>,
"open list:virtiofs" <virtio-fs@redhat.com>
Subject: Re: [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start
Date: Tue, 15 Nov 2022 08:44:31 +0100 [thread overview]
Message-ID: <a0fdeb2a-7b95-d07b-dfce-ae5c6efd6c60@linux.ibm.com> (raw)
In-Reply-To: <20221114121959-mutt-send-email-mst@kernel.org>
Am 14.11.22 um 18:20 schrieb Michael S. Tsirkin:
[...]
>>>>>
>>>>>> This does not seem to fix the regression that I have reported.
>>>>>
>>>>> This was applied on top of 9f6bcfd99f which IIUC does, right?
Just dobble checked,
9f6bcfd99f was the patch that created the original problem, no?
next prev parent reply other threads:[~2022-11-15 7:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 9:22 [PATCH v1 for 7.2 0/9] test and doc updates Alex Bennée
2022-11-08 9:23 ` [PATCH v1 1/9] Run docker probe only if docker or podman are available Alex Bennée
2022-11-08 9:23 ` [PATCH v1 2/9] tests/avocado: improve behaviour waiting for login prompts Alex Bennée
2022-11-08 11:23 ` Philippe Mathieu-Daudé
2022-11-08 21:19 ` John Snow
2022-11-08 9:23 ` [PATCH v1 3/9] tests/avocado/machine_aspeed.py: Reduce noise on the console for SDK tests Alex Bennée
2022-11-08 9:23 ` [PATCH v1 4/9] tests/docker: allow user to override check target Alex Bennée
2022-11-08 11:12 ` Philippe Mathieu-Daudé
2022-11-08 9:23 ` [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start Alex Bennée
2022-11-08 9:32 ` Michael S. Tsirkin
2022-11-08 10:23 ` Alex Bennée
2022-11-08 10:26 ` Michael S. Tsirkin
2022-11-08 11:21 ` Alex Bennée
2022-11-08 15:24 ` Michael S. Tsirkin
2022-11-08 16:41 ` Alex Bennée
2022-11-08 9:33 ` Michael S. Tsirkin
2022-11-14 16:18 ` Christian Borntraeger
2022-11-14 16:37 ` Michael S. Tsirkin
2022-11-14 16:55 ` Christian Borntraeger
2022-11-14 17:10 ` Michael S. Tsirkin
2022-11-14 17:15 ` Christian Borntraeger
2022-11-14 17:20 ` Michael S. Tsirkin
2022-11-15 7:44 ` Christian Borntraeger [this message]
2022-11-15 8:18 ` Christian Borntraeger
2022-11-15 9:05 ` Michael S. Tsirkin
2022-11-15 11:25 ` Michael S. Tsirkin
2022-11-15 13:25 ` Christian Borntraeger
2022-11-15 14:31 ` Alex Bennée
2022-11-15 15:09 ` Christian Borntraeger
2022-11-15 16:05 ` Alex Bennée
2022-11-15 16:40 ` Christian Borntraeger
2022-11-15 16:46 ` Christian Borntraeger
2022-11-21 22:37 ` Michael S. Tsirkin
2022-11-23 6:27 ` Christian Borntraeger
2022-11-14 16:43 ` Alex Bennée
2022-11-08 9:23 ` [PATCH v1 6/9] docs/devel: add a maintainers section to development process Alex Bennée
2022-11-08 9:23 ` [PATCH v1 7/9] docs/devel: make language a little less code centric Alex Bennée
2022-11-08 9:23 ` [PATCH v1 8/9] docs/devel: simplify the minimal checklist Alex Bennée
2022-11-08 9:23 ` [PATCH v1 9/9] docs/devel: try and improve the language around patch review 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=a0fdeb2a-7b95-d07b-dfce-ae5c6efd6c60@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=dgilbert@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mathieu.poirier@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=stefanha@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-fs@redhat.com \
/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).