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 4/6] transport-pci: Correct spelling errors
Date: Fri, 3 Feb 2023 22:16:18 +0200 [thread overview]
Message-ID: <20230203201620.107744-5-parav@nvidia.com> (raw)
In-Reply-To: <20230203201620.107744-1-parav@nvidia.com>
Now that we have individual files, fix reported spelling errors.
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
transport-pci.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/transport-pci.tex b/transport-pci.tex
index 49c35bd..753703f 100644
--- a/transport-pci.tex
+++ b/transport-pci.tex
@@ -981,7 +981,7 @@ \subsubsection{Device Initialization}\label{sec:Virtio Transport Options / Virti
Driver MAY fall back on using INT\#x interrupts for a device
which only supports one MSI-X vector (MSI-X Table Size = 0).
-Driver MAY intepret the Table Size as a hint from the device
+Driver MAY interpret the Table Size as a hint from the device
for the suggested number of MSI-X vectors to use.
Driver MUST NOT attempt to map an event to a vector
--
2.26.2
next prev parent reply other threads:[~2023-02-03 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 20:16 [virtio-comment] [PATCH 0/6] Split transport specific files Parav Pandit
2023-02-03 20:16 ` [PATCH 1/6] transport-pci: Split PCI transport to its own file Parav Pandit
2023-02-03 20:16 ` [PATCH 2/6] transport-mmio: Split MMIO " Parav Pandit
2023-02-03 20:16 ` [PATCH 3/6] transport-channelio: Split Channel IO " Parav Pandit
2023-02-03 20:16 ` Parav Pandit [this message]
2023-02-03 20:16 ` [PATCH 5/6] transport-mmio: Correct spelling errors Parav Pandit
2023-02-16 14:16 ` [virtio-dev] " Cornelia Huck
2023-02-03 20:16 ` [PATCH 6/6] transport-channelio: " 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=20230203201620.107744-5-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.