From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35453) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bUxLH-0000dr-Un for qemu-devel@nongnu.org; Wed, 03 Aug 2016 10:40:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bUxLD-00067k-0B for qemu-devel@nongnu.org; Wed, 03 Aug 2016 10:40:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57516) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bUxLC-00067d-Pt for qemu-devel@nongnu.org; Wed, 03 Aug 2016 10:40:14 -0400 Date: Wed, 3 Aug 2016 17:40:07 +0300 From: "Michael S. Tsirkin" Message-ID: <20160803173405-mutt-send-email-mst@kernel.org> References: <1470043221-37728-1-git-send-email-arei.gonglei@huawei.com> <20160803172932-mutt-send-email-mst@kernel.org> <20160803163328.553e37f1.cornelia.huck@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160803163328.553e37f1.cornelia.huck@de.ibm.com> Subject: Re: [Qemu-devel] [PATCH v6 0/2] virtio-crypto: virtio crypto device specification List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cornelia Huck Cc: Gonglei , 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 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" 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