From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 10 Jan 2023 12:47:09 -0500 From: "Michael S. Tsirkin" Subject: Re: [virtio-dev] Re: [PATCH v2 00/20] Split device spec to its individual files Message-ID: <20230110124607-mutt-send-email-mst@kernel.org> References: <20230109162849.463101-1-parav@nvidia.com> <20230109121857-mutt-send-email-mst@kernel.org> <87358i4ow0.fsf@redhat.com> <87zgaq2z6e.fsf@redhat.com> <87wn5u2yls.fsf@redhat.com> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Disposition: inline To: Parav Pandit Cc: Cornelia Huck , "virtio-dev@lists.oasis-open.org" , "virtio-comment@lists.oasis-open.org" List-ID: On Tue, Jan 10, 2023 at 03:36:28PM +0000, Parav Pandit wrote: > > > From: Cornelia Huck > > Sent: Tuesday, January 10, 2023 10:34 AM > > [..] > > >> Apologies if I sound like a process stickler, but the main problem is > > >> that the ballot is currently about v1 of the patches (and we > > >> obviously can't change that while it is open, as that would > > >> invalidate the votes that already have been cast.) > > > If it auto invalidates, is there any withdrawal process needed? > > > If no, lets withdraw an re-vote on v3. > > > > No, there's no such thing as auto-invalidation, as we cannot modify the ballot > > (sorry if I was unclear.) Let's just withdraw the ballot. > > > No problem. Its clear to me now. > > > > > > >> If your v3 looks good, we need a new ballot to vote on that. As it > > >> stands now, the TC would have voted to include v1 with its known > > >> problems... that's why I think a withdrawal would be best. > > > > > > We will use the same github issue for v3, and new ballot yes? > > > > Yes, exactly. (This is not the first time this has happened.) > > Ok. Please proceed to withdraw. Cornelia will you do this? Parav just a note pls update the link in the description (not in comments - these are ignored) before requesting a new ballot. Thanks! -- MST