From: Cornelia Huck <cohuck@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>,
Jason Wang <jasowang@redhat.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v8] Introduction of Virtio Network device notifications coalescing feature.
Date: Mon, 04 Jul 2022 09:36:14 +0200 [thread overview]
Message-ID: <877d4t2utt.fsf@redhat.com> (raw)
In-Reply-To: <CAJs=3_BuOT07TMFuBwWCBKuV6Mwuy+xd0OehsBMg1bw0EH8-ZQ@mail.gmail.com>
On Thu, Jun 30 2022, Alvaro Karsz <alvaro.karsz@solid-run.com> wrote:
> Thank you Jason.
>
> Cornelia, what happens now?
>
> I'm adding the link to the github issue:
> https://github.com/oasis-tcs/virtio-spec/issues/141
The conflict in the feature bits section is trivial to resolve, so I
think we're good to go. I've opened a ballot.
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-07-04 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 15:05 [virtio-comment] [PATCH v8] Introduction of Virtio Network device notifications coalescing feature Alvaro Karsz
2022-06-27 15:08 ` [virtio-comment] " Alvaro Karsz
2022-06-30 6:22 ` [virtio-comment] " Jason Wang
2022-06-30 7:03 ` Alvaro Karsz
2022-07-04 7:36 ` Cornelia Huck [this message]
2022-07-04 7:38 ` Alvaro Karsz
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=877d4t2utt.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=jasowang@redhat.com \
--cc=virtio-comment@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 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.