Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-dev@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] Re: [PATCH 0/6] Split device spec to its individual files
Date: Sat, 24 Dec 2022 16:30:37 -0500	[thread overview]
Message-ID: <20221224162951-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221224180619.73959-1-parav@nvidia.com>

On Sat, Dec 24, 2022 at 08:06:13PM +0200, Parav Pandit wrote:
> Relatively several of the recent device specification are maintained
> in their own specification file. Such separate files enables better
> maintenance of the specification overall.
> However, several of the initial virtio device specifications
> are located in single file.
> 
> Hence, split them into their individual files.

Makes sense to me.
As a follow-up, how about splitting out conformace sections as well?


> Parav Pandit (6):
>   virtio-scsi: Maintain scsi device spec in separate file
>   virtio-mem-balloon: Maintain memory balloon device spec in separate
>     file
>   virtio-entropy: Maintain entropy device spec in separate file
>   virtio-console: Maintain console device spec in separate file
>   virtio-block: Maintain block device spec in separate file
>   virtio-network: Maintain network device spec in separate file
> 
>  content.tex            | 4535 +---------------------------------------
>  virtio-block.tex       | 1315 ++++++++++++
>  virtio-console.tex     |  233 +++
>  virtio-entropy.tex     |   42 +
>  virtio-mem-balloon.tex |  636 ++++++
>  virtio-network.tex     | 1596 ++++++++++++++
>  virtio-scsi.tex        |  711 +++++++
>  7 files changed, 4539 insertions(+), 4529 deletions(-)
>  create mode 100644 virtio-block.tex
>  create mode 100644 virtio-console.tex
>  create mode 100644 virtio-entropy.tex
>  create mode 100644 virtio-mem-balloon.tex
>  create mode 100644 virtio-network.tex
>  create mode 100644 virtio-scsi.tex
> 
> -- 
> 2.26.2


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/


  parent reply	other threads:[~2022-12-24 21:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 18:06 [virtio-comment] [PATCH 0/6] Split device spec to its individual files Parav Pandit
2022-12-24 18:06 ` [virtio-comment] [PATCH 1/6] virtio-scsi: Maintain scsi device spec in separate file Parav Pandit
2022-12-24 18:06 ` [virtio-comment] [PATCH 2/6] virtio-mem-balloon: Maintain memory balloon " Parav Pandit
2022-12-24 18:06 ` [virtio-comment] [PATCH 3/6] virtio-entropy: Maintain entropy " Parav Pandit
2022-12-24 18:06 ` [virtio-comment] [PATCH 4/6] virtio-console: Maintain console " Parav Pandit
2022-12-24 18:06 ` [virtio-comment] [PATCH 5/6] virtio-block: Maintain block " Parav Pandit
2022-12-24 18:06 ` [virtio-comment] [PATCH 6/6] virtio-network: Maintain network " Parav Pandit
2022-12-24 21:30 ` Michael S. Tsirkin [this message]
2022-12-25  0:26   ` [virtio-comment] Re: [PATCH 0/6] Split device spec to its individual files Parav Pandit

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=20221224162951-mutt-send-email-mst@kernel.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox