From: Parav Pandit <parav@nvidia.com>
To: <mst@redhat.com>, <cohuck@redhat.com>,
<virtio-comment@lists.oasis-open.org>
Cc: <virtio-dev@lists.oasis-open.org>, <shahafs@nvidia.com>,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH] content: Fix type error
Date: Mon, 15 May 2023 18:04:57 +0300 [thread overview]
Message-ID: <20230515150457.760478-1-parav@nvidia.com> (raw)
Fix spelling error from suppling to supplying.
This is on top of [1].
[1] https://lists.oasis-open.org/archives/virtio-comment/202305/msg00101.html
Reported-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
content.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content.tex b/content.tex
index 327926f..9df81b8 100644
--- a/content.tex
+++ b/content.tex
@@ -409,8 +409,8 @@ \section{Driver Notifications} \label{sec:Basic Facilities of a Virtio Device /
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.
+The notification method and supplying any such virtqueue notification config
+data is transport specific.
However, some devices benefit from the ability to find out the
amount of available data in the queue without accessing the virtqueue in memory:
--
2.26.2
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2023-05-15 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 15:04 Parav Pandit [this message]
2023-05-15 15:06 ` [virtio-dev] RE: [PATCH] content: Fix type error 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=20230515150457.760478-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).