All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>
Subject: Re: [virtio-dev] Re: [PATCH v2 00/20] Split device spec to its individual files
Date: Tue, 10 Jan 2023 12:47:09 -0500	[thread overview]
Message-ID: <20230110124607-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481DC75C7AD401B9CE43CCEDCFF9@PH0PR12MB5481.namprd12.prod.outlook.com>

On Tue, Jan 10, 2023 at 03:36:28PM +0000, Parav Pandit wrote:
> 
> > From: Cornelia Huck <cohuck@redhat.com>
> > 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


  reply	other threads:[~2023-01-10 17:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 16:28 [PATCH v2 00/20] Split device spec to its individual files Parav Pandit
2023-01-09 16:28 ` [PATCH v2 01/20] virtio-network: Maintain network device spec in separate directory Parav Pandit
2023-01-09 16:28 ` [PATCH v2 02/20] virtio-network: Fix spelling errors Parav Pandit
2023-01-09 16:28 ` [PATCH v2 03/20] virtio-block: Maintain block device spec in separate directory Parav Pandit
2023-01-09 16:28 ` [PATCH v2 04/20] virtio-console: Maintain console " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 05/20] virtio-entropy: Maintain entropy " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 06/20] virtio-mem-balloon: Maintain mem balloon " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 07/20] virtio-scsi: Maintain scsi host " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 08/20] virtio-gpu: Maintain gpu " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 09/20] virtio-input: Maintain input " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 10/20] virtio-crypto: Maintain crypto " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 11/20] virtio-vsock: Maintain socket " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 12/20] virtio-fs: Maintain file system " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 13/20] virtio-rpmb: Maintain rpmb " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 14/20] virtio-iommu: Maintain iommu " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 15/20] virtio-sound: Maintain sound " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 16/20] virtio-mem: Maintain memory " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 17/20] virtio-i2c: Maintain i2c " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 18/20] virtio-scmi: Maintain scmi " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 19/20] virtio-gpio: Maintain gpio " Parav Pandit
2023-01-09 16:28 ` [PATCH v2 20/20] virtio-pmem: Maintain pmem " Parav Pandit
2023-01-09 17:25 ` [PATCH v2 00/20] Split device spec to its individual files Michael S. Tsirkin
2023-01-10 11:20   ` [virtio-dev] " Cornelia Huck
2023-01-10 15:05     ` Parav Pandit
2023-01-10 15:21       ` [virtio-comment] " Cornelia Huck
2023-01-10 15:26         ` Parav Pandit
2023-01-10 15:33           ` Cornelia Huck
2023-01-10 15:36             ` Parav Pandit
2023-01-10 17:47               ` Michael S. Tsirkin [this message]
2023-01-10 15:46     ` [virtio-comment] " Halil Pasic

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=20230110124607-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    /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.