From: "Michael S. Tsirkin" <mst@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: virtio-comment@lists.linux.dev,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Cornelia Huck" <cohuck@redhat.com>,
"Matias Ezequiel Vara Larsen" <mvaralar@redhat.com>
Subject: Re: [PATCH V10] virtio-transport: Add a section to define mandatory transport requirements
Date: Tue, 3 Sep 2024 06:51:23 -0400 [thread overview]
Message-ID: <20240903065010-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240903103815.pqjdjyedsqy3vr3y@vireshk-i7>
On Tue, Sep 03, 2024 at 04:08:15PM +0530, Viresh Kumar wrote:
> On 14-08-24, 20:27, Viresh Kumar wrote:
> > The current Virtio documentation lacks a set of generic requirements
> > applicable to all transports. Defining these generic requirements could
> > be beneficial when integrating support for a new transport.
> >
> > This section outlines the essential requirements that any transport
> > method must adhere to.
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > V9->V10:
> > - s/multiple// and s/employ/use/
>
> Can we get this merged now please ?
>
> --
You want us to start a vote then?
next prev parent reply other threads:[~2024-09-03 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 14:57 [PATCH V10] virtio-transport: Add a section to define mandatory transport requirements Viresh Kumar
2024-08-21 13:30 ` Matias Ezequiel Vara Larsen
2024-09-03 10:38 ` Viresh Kumar
2024-09-03 10:51 ` Michael S. Tsirkin [this message]
2024-09-03 10:53 ` Viresh Kumar
2024-09-03 11:00 ` Michael S. Tsirkin
2024-09-03 11:07 ` Viresh Kumar
2024-09-03 11:58 ` Stefano Garzarella
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=20240903065010-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mvaralar@redhat.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=virtio-comment@lists.linux.dev \
/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.