From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: "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: [virtio-comment] RE: [virtio-dev] Re: [PATCH v2 00/20] Split device spec to its individual files
Date: Tue, 10 Jan 2023 16:21:13 +0100 [thread overview]
Message-ID: <87zgaq2z6e.fsf@redhat.com> (raw)
In-Reply-To: <PH0PR12MB548116EBA8343DA37A8F345DDCFF9@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, Jan 10 2023, Parav Pandit <parav@nvidia.com> wrote:
>> From: virtio-dev@lists.oasis-open.org <virtio-dev@lists.oasis-open.org> On
>> Behalf Of Cornelia Huck
>>
>> On Mon, Jan 09 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>> > Does makediff still work? Documentation says latexpand does not
>> > support import. without latexdiff generating redlined versions would
>> > be very difficult.
>> >
>> >
>> > I am also worried about consistency since we already use \\input.
>> > If using \\input means putting everything in a single directory,
>> > that's a small price to pay:
>> >
>> > virtio-sound.tex + virtio-sound-conformance.tex
>> >
>> > is not fundamentally worse than device-types/virtio-sound/device.tex
>> > and device-types/virtio-sound/device-conformance.tex
>> >
>> > and it avoids the duplicated "device" in the name.
>> >
>> > Previously it looked like a cosmetic issue, but now it looks like it's
>> > important.
>>
>> I agree, and we need to decide quickly what to do with the ballot. We don't
>> want to merge v1, but the current votes still have a majority of 'yes'. My
>> preference would be to withdraw the ballot, which needs to be done before
>> 22:00 UTC today, if I'm not confused.
>>
>> Parav, what do you think? If you request to withdraw the ballot, that's easy to
>> do; we'll just open a new one once we've agreed on a version.
>
> I am revising the v2 and should be available in 7 pm UTC time.
> This will include,
> a. white space removal at end of the net and blk files
> b. fix missing device conformance links for 4 devices
> c. import to input
> d. continue with directories
> e. rename device-types/<name>/device.tex to device-types/<name>/description.tex
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 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.
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:[~2023-01-10 15:21 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 ` Cornelia Huck [this message]
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
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=87zgaq2z6e.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@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.