From: "Alex Bennée" <alex.bennee@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: virtio-dev@lists.oasis-open.org,
Cornelia Huck <cohuck@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Vincent Guittot <vincent.guittot@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: Tue, 30 Jan 2024 11:28:59 +0000 [thread overview]
Message-ID: <87o7d3oy9w.fsf@draig.linaro.org> (raw)
In-Reply-To: <ac39845f39f1fb17281cfe6472dff590a04e7683.1706602613.git.viresh.kumar@linaro.org> (Viresh Kumar's message of "Tue, 30 Jan 2024 13:58:35 +0530")
Viresh Kumar <viresh.kumar@linaro.org> writes:
> The virtio documentation currently doesn't define any generic
> requirements that are applicable to all transports. They can be useful
> while adding support for a new transport.
>
> This commit tries to define the same.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
LGTM:
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2024-01-30 11:29 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 ` Alex Bennée [this message]
2024-02-12 8:48 ` [virtio-dev] " Viresh Kumar
2024-02-13 12:43 ` Cornelia Huck
2024-02-14 5:56 ` Viresh Kumar
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=87o7d3oy9w.fsf@draig.linaro.org \
--to=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=viresh.kumar@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