From: Parav Pandit <parav@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Cc: "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] Re: [virtio-dev] [virtio 1.3] Feature freeze has started
Date: Fri, 21 Jul 2023 14:21:05 +0000 [thread overview]
Message-ID: <PH0PR12MB548175963F5D563547805173DC3FA@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87h6px8l94.fsf@redhat.com>
> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Cornelia Huck
> Sent: Friday, July 21, 2023 9:09 AM
> > https://github.com/oasis-tcs/virtio-spec/issues/170 ("The size of
> > virtio_net_hdr struct are wrong when VIRTIO_NET_HASH_REPORT feature is
> > negotiated.")
> > * Can someone please check the status of this? Looks like a patch is
> > available, but no progress for a long time? Is this maybe interacting
> > with the inner header hash feature?
> >
> > Any others that I have missed?
>
> Last call for 1.3. The first two are done now, the third one has not seen any
> action, so if anything, it's going to be post-1.3.
>
> I think we're good (and can start preparing for the next steps).
>
Yes, we can do post 1.3.
The fix needs more words than what was posted. I will post one when the branch opens.
---------------------------------------------------------------------
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-07-21 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 12:41 [virtio-dev] [virtio 1.3] Feature freeze has started Cornelia Huck
2023-07-21 13:08 ` Cornelia Huck
2023-07-21 14:21 ` 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=PH0PR12MB548175963F5D563547805173DC3FA@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@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).