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
