From: Parav Pandit <parav@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Subject: [virtio-dev] RE: [virtio-comment] [RFC] virtio 1.3 schedule
Date: Fri, 30 Jun 2023 11:14:37 +0000 [thread overview]
Message-ID: <PH0PR12MB54810A7D2229F4C97E4BF6EEDC2AA@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <877crl49qy.fsf@redhat.com>
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Cornelia Huck
> Sent: Friday, June 30, 2023 4:48 AM
> For the inner header hash, I see there's already an issue (#173), so it's good. I
> have not followed the aq legacy access feature -- if everyone agrees that we
> should be able to vote on it in July, we should have an issue for it as well (I
> cannot find one just by looking at
> titles.)
>
For legacy registers access, it is https://github.com/oasis-tcs/virtio-spec/issues/167
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-06-30 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 13:57 [virtio-dev] [RFC] virtio 1.3 schedule Cornelia Huck
2023-04-05 14:05 ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-04-05 19:23 ` [virtio-dev] Re: [virtio] " Stefan Hajnoczi
2023-04-07 11:24 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-12 16:16 ` Cornelia Huck
2023-06-29 17:41 ` [virtio-dev] " Parav Pandit
2023-06-29 19:35 ` [virtio-dev] " Michael S. Tsirkin
2023-06-30 8:47 ` Cornelia Huck
2023-06-30 8:55 ` Michael S. Tsirkin
2023-06-30 11:14 ` Parav Pandit [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=PH0PR12MB54810A7D2229F4C97E4BF6EEDC2AA@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).