From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: Yan Vugenfirer <yan@daynix.com>, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] Re: [PATCH v2 0/2] define USO feature
Date: Wed, 5 May 2021 07:12:46 -0400 [thread overview]
Message-ID: <20210505071213-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAOEp5OdGmDEGJL8xGhMzxkWgecxNqQ+_uutWQNDBM25xXRVGaw@mail.gmail.com>
Note link to proposal should be part of the issue itself,
not a comment. comments are ignored.
I fixed it up.
On Wed, May 05, 2021 at 01:59:57PM +0300, Yuri Benditovich wrote:
> Hi Michael,
> If there are no more comments, can you please initiate the ballot?
>
> Thanks,
> Yuri Benditovich
>
>
>
> On Wed, Apr 28, 2021 at 9:35 AM Yuri Benditovich
> <yuri.benditovich@daynix.com> wrote:
> >
> > changes v1->v2:
> > Added separate patch fixing mistake in UFO definition
> > Added USO feature explanation
> >
> > Yuri Benditovich (2):
> > virtio-net: fix mistake: segmentation -> fragmentation
> > virtio-net: define USO feature
> >
> > content.tex | 33 ++++++++++++++++++++++-----------
> > 1 file changed, 22 insertions(+), 11 deletions(-)
> >
> > --
> > 2.25.1
> >
>
> 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/
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/
prev parent reply other threads:[~2021-05-05 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 6:35 [virtio-comment] [PATCH v2 0/2] define USO feature Yuri Benditovich
2021-04-28 6:35 ` [virtio-comment] [PATCH v2 1/2] virtio-net: fix mistake: segmentation -> fragmentation Yuri Benditovich
2021-04-28 6:35 ` [virtio-comment] [PATCH v2 2/2] virtio-net: define USO feature Yuri Benditovich
2021-05-05 10:59 ` [virtio-comment] Re: [PATCH v2 0/2] " Yuri Benditovich
2021-05-05 11:12 ` Michael S. Tsirkin [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=20210505071213-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.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.