From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Bertrand Marquis <bertrand.marquis@arm.com>,
virtio-comment@lists.linux.dev,
"Edgar E . Iglesias" <edgar.iglesias@amd.com>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Armelle Laine <armellel@google.com>
Subject: Re: [PATCH v2 0/6] virtio-msg transport layer
Date: Wed, 21 Oct 2026 16:23:51 +0100 [thread overview]
Message-ID: <87mrs7yt4o.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260701181854-mutt-send-email-mst@kernel.org> (Michael S. Tsirkin's message of "Wed, 1 Jul 2026 18:19:30 -0400")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Wed, Jul 01, 2026 at 04:20:47PM +0100, Alex Bennée wrote:
>> Bertrand Marquis <bertrand.marquis@arm.com> writes:
>>
>> > This series adds the virtio-msg transport layer.
>> >
>> > The individuals and organizations involved in this effort have had difficulty in
>> > using the existing virtio-transports in various situations and desire to add one
>> > more transport that performs its transport layer operations by sending and
>> > receiving messages.
>> >
>> > Implementations of virtio-msg will normally be done in multiple layers:
>> > * common / device level
>> > * bus level
>>
>> If there are no comments how long should we leave it before requesting a vote?
>
> for a new transport,during summer vacation time, I'd give it a lot of
> time.
How much more time do you think is needed? I think we are keen to
request a vote soon given we have plenty of working code.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-10-21 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 9:10 [PATCH v2 0/6] virtio-msg transport layer Bertrand Marquis
2026-06-15 9:10 ` [PATCH v2 1/6] virtio-msg: add new command for bus normative Bertrand Marquis
2026-06-15 9:10 ` [PATCH v2 2/6] virtio-msg: Add the FF-A bus bibliography reference Bertrand Marquis
2026-06-15 9:10 ` [PATCH v2 3/6] virtio-msg: Add virtio-msg, a message based virtio transport layer Bertrand Marquis
2026-07-08 15:43 ` Michael Riesch
2026-06-15 9:10 ` [PATCH v2 4/6] virtio-msg: link virtio-msg content Bertrand Marquis
2026-06-15 9:10 ` [PATCH v2 5/6] virtio-msg: add conformance entries in conformance chapter Bertrand Marquis
2026-06-15 9:10 ` [PATCH v2 6/6] virtio-msg: add message transport to core references Bertrand Marquis
2026-07-01 15:20 ` [PATCH v2 0/6] virtio-msg transport layer Alex Bennée
2026-07-01 15:30 ` Parav Pandit
2026-07-01 22:19 ` Michael S. Tsirkin
2026-10-21 15:23 ` Alex Bennée [this message]
2026-10-21 15:42 ` Michael S. Tsirkin
2026-09-01 15:24 ` 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=87mrs7yt4o.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=armellel@google.com \
--cc=arnaud.pouliquen@foss.st.com \
--cc=bertrand.marquis@arm.com \
--cc=edgar.iglesias@amd.com \
--cc=mst@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox