Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Laura Loghin <lauralg@amazon.com>, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v3] vsock: add documentation about len header field
Date: Mon, 11 Apr 2022 16:32:47 +0200	[thread overview]
Message-ID: <874k2zbshc.fsf@redhat.com> (raw)
In-Reply-To: <ef8ed5a1-56ae-9527-0433-09025b2f484a@amazon.com>

On Mon, Apr 11 2022, Laura Loghin <lauralg@amazon.com> wrote:

> On 4/11/22 16:53, Cornelia Huck wrote:
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>>
>>
>>
>> On Thu, Apr 07 2022, Laura Loghin<lauralg@amazon.com>  wrote:
>>
>>> Signed-off-by: Laura Loghin<lauralg@amazon.com>
>>> ---
>>>   virtio-vsock.tex | 5 +++++
>>>   1 file changed, 5 insertions(+)
>> Reviewed-by: Cornelia Huck<cohuck@redhat.com>
>>
>> I guess that needs an issue to be included in 1.3?
>
> I already openedhttps://github.com/oasis-tcs/virtio-spec/issues/137, is there anything else I should do?

The patch should have

Fixes: https://github.com/oasis-tcs/virtio-spec/issues/137

in it (no need to resend, we can include that before pushing as long as
it sits in a reply to the mail); also, please update the issue to point
to the v3 patch.

[We still need to open up the 1.3 branch after some editorial stuff has
been done; then we can hopefully flush the queue of outstanding issues.]


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/


  reply	other threads:[~2022-04-11 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  8:13 [virtio-comment] [PATCH v3] vsock: add documentation about len header field Laura Loghin
2022-04-07 12:04 ` Stefano Garzarella
2022-04-11 13:53 ` Cornelia Huck
2022-04-11 13:58   ` Laura Loghin
2022-04-11 14:32     ` Cornelia Huck [this message]
2022-04-12  9:25       ` Laura Loghin

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=874k2zbshc.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=lauralg@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox