From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] allocating device IDs without a vote
Date: Fri, 30 Oct 2020 10:23:39 +0000 [thread overview]
Message-ID: <20201030102339.GB3046@work-vm> (raw)
In-Reply-To: <20201030061222-mutt-send-email-mst@kernel.org>
* Michael S. Tsirkin (mst@redhat.com) wrote:
> At the Virtio BoF at the virtual KVM forum, 2020, a recurring theme was
> the difficulty contributors face in obtaining device IDs for new
> devices. As allocating a new ID is a technicality, and can not break
> existing devices, it does not sound too bad to skip a voting step in
> that process.
It would seem reasonable to define what the expectations, if any are,
about the use of those IDs:
Is it expected that the allocator of such an ID would eventually
end a request to merge a spec for the device, or are they free
not to?
If merging is expected, then is it acceptable to recycle IDs that have
not been defined after n-Years.
Dave
> I'd like to hear TC's take on such an idea.
>
> This would be similar to the existing standing rule:
>
> Minor cleanups, including editorial formatting changes, spelling
> and typo fixes can be committed directly into git for approval as part
> of the next specification approval ballot.
>
> --
> MST
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2020-10-30 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 10:15 [virtio] allocating device IDs without a vote Michael S. Tsirkin
2020-10-30 10:23 ` Dr. David Alan Gilbert [this message]
2020-10-30 10:30 ` [virtio] Re: [virtio-comment] " Jan Kiszka
2020-10-30 12:16 ` Cornelia Huck
2020-10-30 13:51 ` Mihai Carabas
2020-10-30 14:38 ` Stefan Hajnoczi
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=20201030102339.GB3046@work-vm \
--to=dgilbert@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox