From: Christian Pinto <c.pinto@virtualopensystems.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: virtio-dev@lists.oasis-open.org,
Baptiste Reynal <b.reynal@virtualopensystems.com>,
Jani Kokkonen <Jani.Kokkonen@huawei.com>,
Claudio Fontana <Claudio.Fontana@huawei.com>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [virtio-dev] New virtio device specification
Date: Fri, 10 Jun 2016 10:52:30 +0200 [thread overview]
Message-ID: <CAFZJSOf0mTGO3HhKU=uu7gQ5Pnnvwj2+fnHsLd9dVrs6NUdi+A@mail.gmail.com> (raw)
In-Reply-To: <20160610101549.335c978b.cornelia.huck@de.ibm.com>
Hello Cornelia,
thanks for this clarification. I will immediately start looking into this
and soon release the two patches.
Best,
Christian
On Fri, Jun 10, 2016 at 10:15 AM, Cornelia Huck <cornelia.huck@de.ibm.com>
wrote:
> On Fri, 10 Jun 2016 10:01:05 +0200
> Christian Pinto <c.pinto@virtualopensystems.com> wrote:
>
> > I am writing to understand how to start the procedure to include this
> > device in
> > the virtio specification and get a virtio device ID assigned.
>
> The best way is to prepare some patches against the standard doc (svn
> tree here:
> https://tools.oasis-open.org/version-control/browse/wsvn/virtio/):
> - one patch reserving a device id
> - one patch actually specifying the new device
>
>
> ---------------------------------------------------------------------
> 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:[~2016-06-10 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 8:01 [Qemu-devel] [virtio-dev] New virtio device specification Christian Pinto
2016-06-10 8:15 ` Cornelia Huck
2016-06-10 8:52 ` Christian Pinto [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='CAFZJSOf0mTGO3HhKU=uu7gQ5Pnnvwj2+fnHsLd9dVrs6NUdi+A@mail.gmail.com' \
--to=c.pinto@virtualopensystems.com \
--cc=Claudio.Fontana@huawei.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=b.reynal@virtualopensystems.com \
--cc=cornelia.huck@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.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;
as well as URLs for NNTP newsgroup(s).