From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org
Cc: sgarzare@redhat.com, pasic@linux.ibm.com,
david.edmondson@oracle.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v17 03/11] content: Rename confusing queue_notify_data and vqn names
Date: Mon, 15 May 2023 11:42:56 +0200 [thread overview]
Message-ID: <87cz322an3.fsf@redhat.com> (raw)
In-Reply-To: <20230505014614.571520-4-parav@nvidia.com>
On Fri, May 05 2023, Parav Pandit <parav@nvidia.com> wrote:
> diff --git a/content.tex b/content.tex
> index 9cf938c..327926f 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -405,8 +405,12 @@ \section{Driver Notifications} \label{sec:Basic Facilities of a Virtio Device /
> notification to the device.
>
> When VIRTIO_F_NOTIFICATION_DATA has not been negotiated,
> -this notification involves sending the
> -virtqueue index to the device (method depending on the transport).
> +this notification contains either a virtqueue index if
> +VIRTIO_F_NOTIF_CONFIG_DATA is not negotiated or device supplied virtqueue
> +notification config data if VIRTIO_F_NOTIF_CONFIG_DATA is negotiated.
> +
> +The notification method and suppling any such virtqueue notification config data
> +is transport specific.
Typo: s/suppling/supplying/ (trivial to fix on top)
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-05-15 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 1:46 [virtio-dev] [PATCH v17 00/11] Rename queue number to queue index Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 01/11] content: Add vq index text Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 02/11] content.tex Replace virtqueue number with index Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 03/11] content: Rename confusing queue_notify_data and vqn names Parav Pandit
2023-05-05 8:04 ` [virtio-dev] " David Edmondson
2023-05-15 9:42 ` Cornelia Huck [this message]
2023-05-15 15:10 ` [virtio-dev] " Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 04/11] transport-pci: Avoid first vq index reference Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 05/11] transport-mmio: Rename QueueNum register Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 06/11] transport-mmio: Avoid referring to zero based index Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 07/11] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 08/11] transport-ccw: Refer to the vq by its index Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 09/11] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 10/11] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-05-05 1:46 ` [virtio-dev] [PATCH v17 11/11] virtio-net: Update vqn to vq_index for cvq cmds Parav Pandit
2023-05-11 16:18 ` [virtio-dev] RE: [PATCH v17 00/11] Rename queue number to queue index 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=87cz322an3.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@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