From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, virtio@lists.oasis-open.org
Subject: Re: [virtio-comment] Re: [virtio] [PATCH] virtio: clarify feature negotiation
Date: Thu, 20 Jan 2022 11:52:45 -0500 [thread overview]
Message-ID: <20220120114856-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87k0eud0bi.fsf@redhat.com>
On Thu, Jan 20, 2022 at 02:05:37PM +0100, Cornelia Huck wrote:
> Do we know anything about the state of e.g. hardware implementations?
One I'm aware of is LE and just does not work on BE
platforms in legacy mode. But generally hardware has a standard MTU
so does not need it ...
--
MST
next prev parent reply other threads:[~2022-01-20 16:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 22:50 [virtio-dev] [PATCH] virtio: clarify feature negotiation Michael S. Tsirkin
2022-01-17 15:39 ` Cornelia Huck
2022-01-17 22:26 ` Michael S. Tsirkin
2022-01-19 12:23 ` Halil Pasic
2022-01-19 16:20 ` Michael S. Tsirkin
2022-01-19 17:50 ` [virtio] " Cornelia Huck
2022-01-19 23:48 ` Michael S. Tsirkin
2022-01-20 12:39 ` [virtio-comment] " Cornelia Huck
2022-01-20 15:07 ` Michael S. Tsirkin
2022-01-20 15:24 ` Halil Pasic
2022-01-19 12:23 ` [virtio-comment] Re: [virtio] " Halil Pasic
2022-01-19 16:34 ` Michael S. Tsirkin
2022-01-20 13:05 ` [virtio-dev] " Cornelia Huck
2022-01-20 16:52 ` Michael S. Tsirkin [this message]
2022-01-21 2:38 ` Halil Pasic
2022-01-21 16:05 ` [virtio-dev] " Cornelia Huck
2022-01-24 16:40 ` Halil Pasic
2022-01-24 21:42 ` Michael S. Tsirkin
2022-01-25 14:57 ` [virtio] " Cornelia Huck
2022-01-25 18:05 ` Michael S. Tsirkin
2022-01-26 9:27 ` Jean-Philippe Brucker
2022-04-07 14:28 ` Cornelia Huck
2022-04-07 14:58 ` Michael S. Tsirkin
2022-01-26 15:10 ` Halil Pasic
2022-01-25 15:22 ` [virtio-dev] " Cornelia Huck
2022-01-26 14:14 ` Halil Pasic
2022-01-21 3:17 ` Halil Pasic
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=20220120114856-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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