From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Subject: [virtio-comment] RE: [virtio-dev] [PATCH v2] virtio: Improve queue_reset polarity to match to default reset state
Date: Thu, 28 Apr 2022 09:33:10 +0200 [thread overview]
Message-ID: <8735hxmzm1.fsf@redhat.com> (raw)
In-Reply-To: <PH0PR12MB5481BFEF514B5D7E7B4ED085DCFD9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, Apr 28 2022, Parav Pandit <parav@nvidia.com> wrote:
> All above comments are taken care now with Cornelia's wording for your input and by correctly updating device side section now.
> Sending v3.
Honestly, I think it's a bit early for sending a v3 already, since it
seems we've not reached complete agreement yet what this should look
like in the end, and what we can/should do for 1.2 and what should be
deferred for 1.3. At least, it's about as clear as mud to me. Maybe
someone can summarize?
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2022-04-28 7:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 10:25 [PATCH v2] virtio: Improve queue_reset polarity to match to default reset state Parav Pandit
2022-04-27 11:29 ` [virtio-dev] " Jason Wang
2022-04-27 11:44 ` Xuan Zhuo
2022-04-28 3:46 ` Jason Wang
2022-04-27 14:51 ` Parav Pandit
2022-04-27 15:29 ` Michael S. Tsirkin
2022-04-27 15:39 ` Parav Pandit
2022-04-27 15:43 ` Michael S. Tsirkin
2022-04-27 15:57 ` Parav Pandit
2022-04-27 16:15 ` Parav Pandit
2022-04-27 19:32 ` Michael S. Tsirkin
2022-04-28 1:52 ` Parav Pandit
2022-04-28 3:40 ` Jason Wang
2022-04-28 4:00 ` Parav Pandit
2022-04-28 6:13 ` Jason Wang
2022-04-28 6:30 ` Michael S. Tsirkin
2022-04-28 6:56 ` Jason Wang
2022-04-27 19:28 ` Michael S. Tsirkin
2022-04-27 19:29 ` Parav Pandit
2022-04-28 3:15 ` Jason Wang
2022-04-28 3:24 ` Parav Pandit
2022-04-28 3:43 ` Jason Wang
2022-04-28 4:56 ` Michael S. Tsirkin
2022-04-28 6:10 ` Jason Wang
2022-04-28 6:26 ` Michael S. Tsirkin
2022-04-28 8:20 ` Jason Wang
2022-04-27 12:48 ` [virtio-dev] " Cornelia Huck
2022-04-28 1:09 ` [virtio-dev] " Parav Pandit
2022-04-27 20:39 ` [virtio-dev] " Michael S. Tsirkin
2022-04-28 1:49 ` Parav Pandit
2022-04-28 7:33 ` Cornelia Huck [this message]
2022-04-28 19:13 ` Parav Pandit
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=8735hxmzm1.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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 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.