From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: linux-s390@vger.kernel.org, markver@us.ibm.com,
Xie Yongji <xieyongji@bytedance.com>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
stefanha@redhat.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>
Subject: Re: [PATCH v3 1/1] virtio: write back F_VERSION_1 before validate
Date: Wed, 13 Oct 2021 08:55:03 -0400 [thread overview]
Message-ID: <20211013085423-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87zgrdulwp.fsf@redhat.com>
On Wed, Oct 13, 2021 at 02:52:38PM +0200, Cornelia Huck wrote:
> On Wed, Oct 13 2021, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Wed, Oct 13, 2021 at 01:23:50PM +0200, Christian Borntraeger wrote:
> >> Can we get this kernel patch queued for 5.15 and stable without waiting for the QEMU patch
> >> as we have a regression with 4.14?
> >
> > Probably. Still trying to decide between this and plain revert for 5.15
> > and back. Maybe both?
>
> Probably better queue this one, in case we have some undiscovered
> problems with the config space access in virtio-net?
So both then. I think you are right. Pushed out to -next. Will do a pull
towards end of the week.
--
MST
prev parent reply other threads:[~2021-10-13 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 5:39 [PATCH v3 1/1] virtio: write back F_VERSION_1 before validate Halil Pasic
2021-10-11 9:07 ` Cornelia Huck
2021-10-13 10:10 ` Michael S. Tsirkin
2021-10-13 11:23 ` Christian Borntraeger
2021-10-13 12:24 ` Michael S. Tsirkin
2021-10-13 12:44 ` Halil Pasic
2021-10-13 12:46 ` Michael S. Tsirkin
2021-10-13 12:52 ` Cornelia Huck
2021-10-13 12:55 ` 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=20211013085423-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=markver@us.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.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).