From: Viresh Kumar <viresh.kumar@linaro.org>
To: Cornelia Huck <cohuck@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
"Michael S. Tsirkin" <mst@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
stratos-dev@op-lists.linaro.org,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>
Subject: [virtio-dev] Re: [PATCH V2] virtio-transport: Clarify requirements
Date: Wed, 14 Feb 2024 11:26:09 +0530 [thread overview]
Message-ID: <20240214055609.t3t3kv7mmxtcfkeh@vireshk-i7> (raw)
In-Reply-To: <87a5o4h6v6.fsf@redhat.com>
On 13-02-24, 13:43, Cornelia Huck wrote:
> Apart from the nits above, this looks good to me.
>
> I'd be in favour of initiating a vote for this, after the OASIS
> infrastructure migragion has completed and we have dealt with any
> fallout from that... that would probably mean March :(
That's fine.
> (Oh, and this should probably go to virtio-comment as well.)
Resent now.
> [Apologies for not reviewing earlier, but I'm struggling to keep afloat,
> and the OASIS infrastructure saga did not exactly help...]
No issues :)
--
viresh
---------------------------------------------------------------------
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:[~2024-02-14 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 8:28 [virtio-dev] [PATCH V2] virtio-transport: Clarify requirements Viresh Kumar
2024-01-30 11:28 ` [virtio-dev] " Alex Bennée
2024-02-12 8:48 ` Viresh Kumar
2024-02-13 12:43 ` Cornelia Huck
2024-02-14 5:56 ` Viresh Kumar [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=20240214055609.t3t3kv7mmxtcfkeh@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mst@redhat.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=virtio-dev@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).