From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v5 0/6] Split transport specific files
Date: Fri, 3 Mar 2023 02:45:50 -0500 [thread overview]
Message-ID: <20230303024543-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54810629E248D17C25CF5B1CDCB29@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, Mar 02, 2023 at 03:10:45PM +0000, Parav Pandit wrote:
>
>
> > From: Parav Pandit <parav@nvidia.com>
> > Sent: Friday, February 24, 2023 5:22 PM
> >
> > 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
> >
> Other patches on top of this needs it.
>
> Please create a voting ballot for this series.
Done, thanks for doing this.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-03-03 7:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 22:22 [PATCH v5 0/6] Split transport specific files Parav Pandit
2023-02-24 22:22 ` [virtio-dev] " Parav Pandit
2023-02-24 22:22 ` [PATCH v5 1/6] transport-pci: Split PCI transport to its own file Parav Pandit
2023-02-24 22:22 ` [virtio-dev] " Parav Pandit
2023-02-24 22:22 ` [PATCH v5 2/6] transport-mmio: Split MMIO " Parav Pandit
2023-02-24 22:22 ` [virtio-dev] " Parav Pandit
2023-02-24 22:22 ` [PATCH v5 3/6] transport-ccw: Split Channel IO " Parav Pandit
2023-02-24 22:22 ` [virtio-dev] " Parav Pandit
2023-02-24 22:22 ` [PATCH v5 4/6] transport-pci: Fix spellings and white spaces Parav Pandit
2023-02-24 22:22 ` [virtio-dev] " Parav Pandit
2023-02-24 22:22 ` [PATCH v5 5/6] transport-mmio: " Parav Pandit
2023-02-24 22:22 ` [virtio-dev] " Parav Pandit
2023-02-24 22:22 ` [PATCH v5 6/6] transport-ccw: " Parav Pandit
2023-02-24 22:22 ` [virtio-dev] " Parav Pandit
2023-03-02 15:10 ` [virtio-dev] RE: [PATCH v5 0/6] Split transport specific files Parav Pandit
2023-03-03 7:45 ` Michael S. Tsirkin [this message]
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=20230303024543-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.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