All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"mst@redhat.com" <mst@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
	"Crasta Denis-B22176" <denis.crasta@freescale.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"'Ola Liljedahl@arm.com'" <Ola.Liljedahl@arm.com>,
	"'Venkatesan, Venky'" <venky.venkatesan@intel.com>,
	"Hanweidong (Randy)" <hanweidong@huawei.com>,
	"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Mihai Claudiu Caraman" <mike.caraman@nxp.com>,
	"'François-Frédéric Ozog'" <ff.ozog@6wind.com>,
	"Catalin Vasile" <cata.vasile@nxp.com>,
	"Zhoujian (jay, Euler)" <jianjay.zhou@huawei.com>,
	"Varun Sethi" <Varun.Sethi@freescale.com>,
	"Jani Kokkonen" <Jani.Kokkonen@huawei.com>,
	"Lingli Deng" <denglingli@chinamobile.com>,
	"'Karlsson, Magnus'" <magnus.karlsson@intel.com>
Subject: Re: [Qemu-devel] [RFC v2] virtio-crypto specification
Date: Thu, 14 Apr 2016 12:45:26 +0200	[thread overview]
Message-ID: <20160414124526.075ebe9a.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B031569B@SZXEMA503-MBS.china.huawei.com>

On Thu, 14 Apr 2016 10:36:14 +0000
"Gonglei (Arei)" <arei.gonglei@huawei.com> wrote:

> > The main spec text is in trunk/content.tex.  You also need to modify
> > trunk/conformance.tex to include all the "Driver Requirements" and
> > "Device Requirements" sections for your device.
> > 
> 
> Thank you for your reminder, Stefan. Because the virtio-crypto spec is still under review,
> I just need to submit a patch to reserve a device id for crypto device at present. Right?

Yes. We should be able to integrate it together with the reserved vsock
id.

Michael: We'll probably need to open issues for the id reservation,
don't we?

      reply	other threads:[~2016-04-14 10:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  9:14 [Qemu-devel] [RFC v2] virtio-crypto specification Gonglei (Arei)
2016-04-11  9:43 ` [Qemu-devel] [virtio-dev] " Stefan Hajnoczi
2016-04-11 11:17   ` Gonglei (Arei)
2016-04-12  8:00 ` [Qemu-devel] " Cornelia Huck
2016-04-12  9:03   ` Gonglei (Arei)
2016-04-13 16:29     ` Cornelia Huck
2016-04-14  3:33       ` Gonglei (Arei)
2016-04-14  7:58         ` Cornelia Huck
2016-04-14  9:26           ` Gonglei (Arei)
2016-04-14 10:14             ` Cornelia Huck
2016-04-14 10:22             ` Michael S. Tsirkin
2016-04-14 10:31               ` Gonglei (Arei)
2016-04-14 10:26             ` Stefan Hajnoczi
2016-04-14 10:36               ` Gonglei (Arei)
2016-04-14 10:45                 ` Cornelia Huck [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=20160414124526.075ebe9a.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=Ola.Liljedahl@arm.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=arei.gonglei@huawei.com \
    --cc=cata.vasile@nxp.com \
    --cc=denglingli@chinamobile.com \
    --cc=denis.crasta@freescale.com \
    --cc=ff.ozog@6wind.com \
    --cc=hanweidong@huawei.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=magnus.karlsson@intel.com \
    --cc=mike.caraman@nxp.com \
    --cc=mst@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=venky.venkatesan@intel.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 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.