From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: Requesting ballots for #31 and #32
Date: Tue, 12 Feb 2019 21:04:35 -0500 [thread overview]
Message-ID: <20190212205956-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190213013813.GA14307@stefanha-x1.localdomain>
On Wed, Feb 13, 2019 at 09:38:13AM +0800, Stefan Hajnoczi wrote:
> Hi,
> I'd like to request ballots for the following issues:
>
> "content: reserve virtio device ID for file system devices"
> https://github.com/oasis-tcs/virtio-spec/issues/31
>
> "virtio-blk: discard and write zeroes clarifications"
> https://github.com/oasis-tcs/virtio-spec/issues/32
>
> At least #32 is needed for VIRTIO 1.1 but #31 is trivial and will
> prevent device ID conflicts so I suggest merging it too.
>
> Thank you,
> Stefan
Would you say that #32 is a material change or not?
"Material Change" is any change to the content of a Work Product that
that would require a compliant application or implementation to be
modified or rewritten in order to remain compliant or which adds new
features or otherwise expands the scope of the work product.
I think you indicated in the past that it isn't.
However I think #31 would be a new feature. If yes including it would not
qualify as non material change and that would force
another public review round.
Would you agree?
If doesn't seem worth forcing a public review for a trivial change.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2019-02-13 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 1:38 [virtio-dev] Requesting ballots for #31 and #32 Stefan Hajnoczi
2019-02-13 2:04 ` Michael S. Tsirkin [this message]
2019-02-13 9:11 ` [virtio-dev] " 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=20190212205956-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=stefanha@redhat.com \
--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.