All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Gonglei <arei.gonglei@huawei.com>,
	qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
	peter.huangpeng@huawei.com, luonengjun@huawei.com,
	stefanha@redhat.com, denglingli@chinamobile.com,
	Jani.Kokkonen@huawei.com, Ola.Liljedahl@arm.com,
	Varun.Sethi@freescale.com, xin.zeng@intel.com,
	brian.a.keating@intel.com, liang.j.ma@intel.com,
	john.griffin@intel.com, hanweidong@huawei.com,
	weidong.huang@huawei.com
Subject: Re: [Qemu-devel] [PATCH v6 0/2] virtio-crypto: virtio crypto device specification
Date: Wed, 3 Aug 2016 17:40:07 +0300	[thread overview]
Message-ID: <20160803173405-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20160803163328.553e37f1.cornelia.huck@de.ibm.com>

On Wed, Aug 03, 2016 at 04:33:28PM +0200, Cornelia Huck wrote:
> On Wed, 3 Aug 2016 17:30:22 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > On Mon, Aug 01, 2016 at 05:20:19PM +0800, Gonglei wrote:
> > > This is the specification (version 6) about a new virtio crypto device.
> > > After a big reconstruction, the spec (symmetric algos) is near to stabilize.
> > > This version fix some problems of formating and return value, etc.
> > > 
> > > If you have any comments, please let me know, thanks :)
> > 
> > You might want to open a jira tracker in oasis jira to add this.
> 
> It may make sense to open one/many jira trackers to reserve the device
> ids (for the various device types that have accumulated) at least.

Yes! Can you do this please?
As a reminder for new people, the process works like this:

- when you want patches to be considered
  for spec inclusion, make sure there's a
  jira issue (if you don't have jira access, let me know pls),
  and include the issue number in patch submitted to mailing list, on a line
  by itself e.g.

VIRTIO-123

- summarize change in proposal field
  add link to patch in archives (gmane or oasis
  archives)

- in Fix Version/s, please include future versions which
  should include the fix.

- in environment, pls list who reported this, and if
  the comment was submitted on virtio-comments or
  the oasis web form, pls mention this.

- when you want people to vote,
  move issue to open state, and send me a reminder.


I have a tool that, given the issue number, will:

- copy title and number to ballot title.
- fill in versions to include change in question field.
- fill proposal is description field.

and will then start a 7-day ballot to approve inclusion
in relevant spec version(s).

-- 
MST

  reply	other threads:[~2016-08-03 14:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01  9:20 [Qemu-devel] [PATCH v6 0/2] virtio-crypto: virtio crypto device specification Gonglei
2016-08-01  9:20 ` [Qemu-devel] [PATCH v6 1/2] virtio-crypto: Add " Gonglei
2016-08-04  7:48   ` Zeng, Xin
2016-08-04 11:24     ` Gonglei (Arei)
2016-08-04 19:56       ` Michael S. Tsirkin
2016-08-08  6:27         ` Zeng, Xin
2016-08-09 10:44           ` Cornelia Huck
2016-08-09 13:42             ` Zeng, Xin
2016-08-09 10:58           ` Michael S. Tsirkin
2016-08-09 13:42             ` Zeng, Xin
2016-08-10  1:11               ` Gonglei (Arei)
2016-08-01  9:20 ` [Qemu-devel] [PATCH v6 2/2] virtio-crypto: add conformance clauses Gonglei
2016-08-03 14:30 ` [Qemu-devel] [PATCH v6 0/2] virtio-crypto: virtio crypto device specification Michael S. Tsirkin
2016-08-03 14:33   ` Cornelia Huck
2016-08-03 14:40     ` Michael S. Tsirkin [this message]
2016-08-03 14:53       ` Cornelia Huck
2016-08-03 17:23         ` Cornelia Huck
2016-08-03 18:40           ` Michael S. Tsirkin
2016-08-04 19:50           ` Michael S. Tsirkin
2016-08-03 15:17   ` Zeng, Xin
2016-08-03 15:46     ` Michael S. Tsirkin

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=20160803173405-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=Ola.Liljedahl@arm.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=arei.gonglei@huawei.com \
    --cc=brian.a.keating@intel.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=denglingli@chinamobile.com \
    --cc=hanweidong@huawei.com \
    --cc=john.griffin@intel.com \
    --cc=liang.j.ma@intel.com \
    --cc=luonengjun@huawei.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=weidong.huang@huawei.com \
    --cc=xin.zeng@intel.com \
    /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.