From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-return-3168-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Date: Thu, 2 Aug 2018 01:30:16 +0300 From: "Michael S. Tsirkin" Message-ID: <20180802012748-mutt-send-email-mst@kernel.org> References: <1529929292-11900-1-git-send-email-pasic@linux.ibm.com> <20180703030130-mutt-send-email-mst@kernel.org> <2cbc368b-de0c-563e-3524-7f54bfe37d1e@linux.ibm.com> <71c9fa95-b672-e51e-cc5a-a754fe033ee9@linux.ibm.com> <477abdb8-93c4-5ff6-17b2-0f3ed1a829a4@linux.ibm.com> <20180727143700-mutt-send-email-mst@kernel.org> <38436869-1a5e-9d17-a1fb-a6049f0f8bd5@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <38436869-1a5e-9d17-a1fb-a6049f0f8bd5@linux.ibm.com> Subject: Re: [virtio] Re: [virtio-dev] Re: [virtio] Re: [virtio-dev] [PATCH v3 0/6] rework notifications terminology To: Halil Pasic Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org, Cornelia Huck , Pawel Moll , Stefan Hajnoczi List-ID: On Wed, Aug 01, 2018 at 03:04:54PM +0200, Halil Pasic wrote: >=20 >=20 > On 07/27/2018 01:45 PM, Michael S. Tsirkin wrote: > > On Fri, Jul 27, 2018 at 01:33:15PM +0200, Halil Pasic wrote: > > >=20 > > >=20 > > > On 07/17/2018 06:47 PM, Halil Pasic wrote: > > > > > > >=20 > > > > > > > OK=A0I=A0see=A0there=A0are=A0acks=A0already=A0-=A0do=A0you=A0= want=A0to=A0start=A0voting=A0on=A0this? > > > > > > >=20 > > > > > > >=20 > > > > > > >=20 > > > > > >=20 > > > > > > Yes,=A0voting=A0would=A0make=A0sense=A0in=A0my=A0opinion. > > > > > >=20 > > > > >=20 > > > > >=20 > > > > > I've=A0submitted=A0a=A0github=A0issue.=A0Please=A0let=A0me=A0know= =A0if=A0further=A0actions=A0are > > > > > required. > > > > >=20 > > > >=20 > > > > ping > > >=20 > > > ping > >=20 > > Oh, sorry, I wasn't clear. > > What you want to do is > > 1. post the patches including > > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/16 > > in the commit log part. > > 2. proposal must link to oasis archive, not mail-archive. > >=20 > > Anyway, I fixed the link and started voting now. > >=20 >=20 > Should post a v4 (or a 'REPOST v3') with the r-b's received for > v3 and the 'Fixes' tags? I mean the ballot, would not link to the > final thread then. I'm a bit confused regarding now, but I > think I understood the process. I think you are right since ballot started no need for v4. > FYI I'm on and off starting tomorrow till 5th September. I > am very likely to make any ballots though, but longer response > times and lower availability are to be expected. >=20 > Thanks, > Halil What are we going to do about crypto proposals? I think we do want to finalize a draft for public review by september, and it seems very unfortunate not to have that device in the draft at all. --=20 MST --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that=20 generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php=20