From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: virtio-dev@lists.oasis-open.org
Cc: mst@redhat.com, cohuck@redhat.com, stefanha@redhat.com
Subject: [virtio-dev] ping: virtio-fs stuff
Date: Mon, 10 Jun 2019 11:36:39 +0100 [thread overview]
Message-ID: <20190610103638.GC22439@work-vm> (raw)
Hi,
Can I give a gentle ping for the set of virtio-fs related things;
a) Reservation of an ID
https://github.com/oasis-tcs/virtio-spec/issues/31
b) Shared memory regions
https://github.com/oasis-tcs/virtio-spec/issues/40
c) Review of the virito-fs spec
https://lists.oasis-open.org/archives/virtio-dev/201904/msg00022.html
(a) is just a reservation - so should be pretty easy?
(b) I've seen other suggested uses, but I don't think I've
seen any other suggestions for changes.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
reply other threads:[~2019-06-10 10:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190610103638.GC22439@work-vm \
--to=dgilbert@redhat.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=stefanha@redhat.com \
--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