From: Cornelia Huck <cohuck@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>, mst@redhat.com
Cc: virtio-comment@lists.oasis-open.org, jasowang@redhat.com,
stefanha@redhat.com, arseny.krasnov@kaspersky.com
Subject: [virtio-comment] Re: [PATCH v12 0/3] virtio-vsock: SOCK_SEQPACKET description
Date: Fri, 14 Jan 2022 11:08:55 +0100 [thread overview]
Message-ID: <874k66wrwo.fsf@redhat.com> (raw)
In-Reply-To: <20220114093952.gjn3mm6mg6wlyibv@steredhat>
On Fri, Jan 14 2022, Stefano Garzarella <sgarzare@redhat.com> wrote:
> Cornelia, Michael,
> if you are happy with this version, can we start the vote to have these
> changes in virtio-spec 1.2?
Looks good to me. Unless there are objections, I'll start the vote later
today.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/132
>
> Thanks,
> Stefano
>
> On Thu, Jan 13, 2022 at 05:51:59PM +0100, Stefano Garzarella wrote:
>>v12:
>>- added statement about supporting F_STREAM when F_SEQPACKET is negotiated
>> [cohuck, mst]
>>
>>v11: https://lists.oasis-open.org/archives/virtio-comment/202201/msg00027.html
>>- reworked "Message and record boundaries" paragraph [stefanha]
>>
>>Linux kernel and QEMU already merged SOCK_SEQPACKET support,
>>so I'm resending Arseny's patches to have consistent virtio-spec
>>and implementation.
>>
>>I added patch 2, following the discussion about F_STREAM feature bit:
>>https://markmail.org/message/aoaspjy2jhidwbuo#query:+page:1+mid:obw54zzikgqimhjk+state:results
>>
>>Thanks,
>>Stefano
>>
>>Arseny Krasnov (2):
>> virtio-vsock: use C style defines for constants
>> virtio-vsock: SOCK_SEQPACKET description
>>
>>Stefano Garzarella (1):
>> virtio-vsock: add VIRTIO_VSOCK_F_STREAM feature bit
>>
>> virtio-vsock.tex | 88 +++++++++++++++++++++++++++++++++---------------
>> 1 file changed, 60 insertions(+), 28 deletions(-)
>>
>>--
>>2.31.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/
next prev parent reply other threads:[~2022-01-14 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 16:51 [PATCH v12 0/3] virtio-vsock: SOCK_SEQPACKET description Stefano Garzarella
2022-01-13 16:52 ` [PATCH v12 1/3] virtio-vsock: use C style defines for constants Stefano Garzarella
2022-01-13 16:52 ` [virtio-comment] [PATCH v12 2/3] virtio-vsock: add VIRTIO_VSOCK_F_STREAM feature bit Stefano Garzarella
2022-01-13 16:52 ` [PATCH v12 3/3] virtio-vsock: SOCK_SEQPACKET description Stefano Garzarella
2022-01-14 9:39 ` [PATCH v12 0/3] " Stefano Garzarella
2022-01-14 10:08 ` Cornelia Huck [this message]
2022-01-14 17:58 ` Michael S. Tsirkin
2022-01-17 9:33 ` Stefano Garzarella
2022-01-17 9:46 ` [virtio-comment] " Arseny Krasnov
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=874k66wrwo.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=arseny.krasnov@kaspersky.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@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.