All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Hanweidong (Randy)" <hanweidong@huawei.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	"mst@redhat.com" <mst@redhat.com>,
	Lingli Deng <denglingli@chinamobile.com>,
	Jani Kokkonen <Jani.Kokkonen@huawei.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.com>,
	"'Ola Liljedahl@arm.com'" <Ola.Liljedahl@arm.com>,
	Varun Sethi <Varun.Sethi@freescale.com>
Subject: Re: [Qemu-devel] [virtio-dev] RE: [RFC v4] virtio-crypto specification
Date: Thu, 14 Jul 2016 13:21:59 +0100	[thread overview]
Message-ID: <20160714122159.GA16535@stefanha-x1.localdomain> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B0357FB1@SZXEMA503-MBS.china.huawei.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

On Fri, Jul 08, 2016 at 07:27:59AM +0000, Gonglei (Arei) wrote:
> Ping...
> 
> I'd like to know what's the process of a new virtio device can be merged? 
> Anybody can tell me? Thanks a lot.
> 
> Taking Virtio-gpu as an example, the virtio-gpu had been merged in Linux kernel
> And Qemu communities, but the corresponding virtio-gpu spec hadn't been merged
> yet. Why was that? Am I missing some rules? Thanks. 

That's the wrong way around and should be avoided.  It would be bad if
guests started running with drivers that don't implement the same
specification as QEMU.

Therefore the virtio spec should be merged first.  Maybe the Linux
driver can be merged under staging or marked experimental, but it should
not be considered stable before the spec has been accepted by the VIRTIO
Technical Committee.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-07-14 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26  9:35 [Qemu-devel] [RFC v4] virtio-crypto specification Gonglei (Arei)
2016-07-08  7:27 ` Gonglei (Arei)
2016-07-14 12:16   ` Stefan Hajnoczi
2016-07-14 12:21   ` Stefan Hajnoczi [this message]
2016-07-22  0:48 ` Zeng, Xin
2016-07-22  2:52   ` Gonglei (Arei)
2016-07-22  5:31     ` Zeng, Xin
2016-07-25  1:38       ` Gonglei (Arei)
2016-07-25  6:19         ` Zeng, Xin
2016-07-25  7:16           ` Gonglei (Arei)

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=20160714122159.GA16535@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=Ola.Liljedahl@arm.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=arei.gonglei@huawei.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=denglingli@chinamobile.com \
    --cc=hanweidong@huawei.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=mst@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.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 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.