From: Parav Pandit <parav@nvidia.com>
To: "mst@redhat.com" <mst@redhat.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [virtio-dev] RE: [PATCH v2] transport-mmio: Replace virtual queue with virtqueue
Date: Thu, 11 May 2023 16:33:49 +0000 [thread overview]
Message-ID: <PH0PR12MB54814C6590DCF50CFAC66720DC749@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230511163020.708427-1-parav@nvidia.com>
> From: Parav Pandit <parav@nvidia.com>
> Sent: Thursday, May 11, 2023 12:30 PM
>
> Basic facilities define the virtqueue construct for device <-> driver
> communication.
>
> PCI transport and individual devices description also refers to it as virtqueue.
>
> MMIO refers to it as 'virtual queue'.
>
> Align MMIO transport description to call such object a virtqueue.
>
> This patch is on top of [1].
>
>
> [1] https://lists.oasis-open.org/archives/virtio-
> comment/202305/msg00101.html
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/168
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> changelog:
> v1->v2:
> - no change, only rebased on top of [1].
>
This has no change from mid-April to now.
Only rebase on top of [1].
Can you please start the vote on this editorial change as well?
---------------------------------------------------------------------
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-05-11 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 16:30 [virtio-dev] [PATCH v2] transport-mmio: Replace virtual queue with virtqueue Parav Pandit
2023-05-11 16:33 ` Parav Pandit [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=PH0PR12MB54814C6590DCF50CFAC66720DC749@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=shahafs@nvidia.com \
--cc=stefanha@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).