From: Parav Pandit <parav@nvidia.com>
To: mst@redhat.com, virtio-dev@lists.oasis-open.org, cohuck@redhat.com
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
Parav Pandit <parav@nvidia.com>
Subject: [PATCH v1 0/6] Split transport specific files
Date: Fri, 17 Feb 2023 03:30:02 +0200 [thread overview]
Message-ID: <20230217013008.16062-1-parav@nvidia.com> (raw)
Problem statement:
Currently several tens of pages worth of transport specification
is situated in single file. Many parts of the specification
are already maintained in separate files.
Such separate files enables better maintenance of the specification overall.
Solution:
Follow the approach similar to rest of the spec, and keep
transport specific spec in their individual files.
This series is for fixing issue [1].
[1] Fixes: https://github.com/oasis-tcs/virtio-spec/issues/157
Please review.
Patch summary:
patch 1 moves pci transport to its own file
patch 2 moves mmio transport to its own file
patch 3 moves channel io transport to its own file
patch 4 to 6 fixes spelling errors existed in the spec which are
discovered during splitting the files
Parav Pandit (6):
transport-pci: Split PCI transport to its own file
transport-mmio: Split MMIO transport to its own file
transport-channelio: Split Channel IO transport to its own file
transport-pci: Correct spelling errors
transport-mmio: Correct spelling errors
transport-channelio: Correct spelling errors
content.tex | 2318 +--------------------------------------
transport-channelio.tex | 601 ++++++++++
transport-mmio.tex | 552 ++++++++++
transport-pci.tex | 1160 ++++++++++++++++++++
4 files changed, 2316 insertions(+), 2315 deletions(-)
create mode 100644 transport-channelio.tex
create mode 100644 transport-mmio.tex
create mode 100644 transport-pci.tex
--
2.26.2
next reply other threads:[~2023-02-17 1:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 1:30 Parav Pandit [this message]
2023-02-17 1:30 ` [PATCH v1 1/6] transport-pci: Split PCI transport to its own file Parav Pandit
2023-02-17 1:30 ` [PATCH v1 2/6] transport-mmio: Split MMIO " Parav Pandit
2023-02-17 1:30 ` [PATCH v1 3/6] transport-channelio: Split Channel IO " Parav Pandit
2023-02-17 1:30 ` [PATCH v1 4/6] transport-pci: Correct spelling errors Parav Pandit
2023-02-17 1:30 ` [PATCH v1 5/6] transport-mmio: " Parav Pandit
2023-02-17 10:26 ` Michael S. Tsirkin
2023-02-17 15:59 ` Parav Pandit
2023-02-17 1:30 ` [PATCH v1 6/6] transport-channelio: " Parav Pandit
2023-02-17 9:14 ` Michael S. Tsirkin
2023-02-17 13:58 ` [virtio-comment] " 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=20230217013008.16062-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=shahafs@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