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 v5 6/6] transport-ccw: Fix spellings and white spaces
Date: Sat, 25 Feb 2023 00:22:15 +0200 [thread overview]
Message-ID: <20230224222215.339715-7-parav@nvidia.com> (raw)
In-Reply-To: <20230224222215.339715-1-parav@nvidia.com>
Now that we have individual files, fix reported spelling errors.
While at it, remove extra white spaces.
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/157
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v1->v2:
- remove trailing white spaces
---
transport-ccw.tex | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/transport-ccw.tex b/transport-ccw.tex
index 93401a4..c492cb9 100644
--- a/transport-ccw.tex
+++ b/transport-ccw.tex
@@ -56,13 +56,13 @@ \subsection{Basic Concepts}\label{sec:Virtio Transport Options / Virtio over cha
\end{tabular}
A virtio-ccw proxy device facilitates:
-\begin{itemize}
+\begin{itemize}
\item Discovery and attachment of virtio devices (as described above).
\item Initialization of virtqueues and transport-specific facilities (using
virtio-specific channel commands).
\item Notifications (via hypercall and a combination of I/O interrupts
and indicator bits).
-\end{itemize}
+\end{itemize}
\subsubsection{Channel Commands for Virtio}\label{sec:Virtio Transport Options / Virtio
over channel I/O / Basic Concepts/ Channel Commands for Virtio}
@@ -107,7 +107,7 @@ \subsubsection{Notifications}\label{sec:Virtio Transport Options / Virtio
Host->Guest Notification / Notification via Classic I/O Interrupts} and
\ref{sec:Virtio Transport Options / Virtio over channel I/O / Device
Operation / Host->Guest Notification / Notification via Adapter I/O
-Interrupts} respectively.
+Interrupts} respectively.
Configuration change notifications are done using so-called classic I/O
interrupts. The initialization is described in section \ref{sec:Virtio
@@ -413,7 +413,7 @@ \subsubsection{Setting Up Indicators}\label{sec:Virtio Transport Options / Virti
\begin{itemize}
\item a summary indicator byte covering the virtqueues for one or more
virtio-ccw proxy devices
-\item a set of contigous indicator bits for the virtqueues for a
+\item a set of contiguous indicator bits for the virtqueues for a
virtio-ccw proxy device
\end{itemize}
@@ -563,7 +563,7 @@ \subsubsection{Guest->Host Notification}\label{sec:Virtio Transport Options / Vi
\drivernormative{\paragraph}{Guest->Host Notification}{Virtio Transport Options / Virtio over channel I/O / Device Operation / Guest->Host Notification}
-For each notification, the driver SHOULD use GPR4 to pass the host cookie received in GPR2 from the previous notication.
+For each notification, the driver SHOULD use GPR4 to pass the host cookie received in GPR2 from the previous notification.
\begin{note}
For example:
--
2.26.2
WARNING: multiple messages have this Message-ID (diff)
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: [virtio-dev] [PATCH v5 6/6] transport-ccw: Fix spellings and white spaces
Date: Sat, 25 Feb 2023 00:22:15 +0200 [thread overview]
Message-ID: <20230224222215.339715-7-parav@nvidia.com> (raw)
Message-ID: <20230224222215.scheGgrKVPQWQFbeLYzTREghsmwc_osgoEc5X9qj2H0@z> (raw)
In-Reply-To: <20230224222215.339715-1-parav@nvidia.com>
Now that we have individual files, fix reported spelling errors.
While at it, remove extra white spaces.
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/157
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
changelog:
v1->v2:
- remove trailing white spaces
---
transport-ccw.tex | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/transport-ccw.tex b/transport-ccw.tex
index 93401a4..c492cb9 100644
--- a/transport-ccw.tex
+++ b/transport-ccw.tex
@@ -56,13 +56,13 @@ \subsection{Basic Concepts}\label{sec:Virtio Transport Options / Virtio over cha
\end{tabular}
A virtio-ccw proxy device facilitates:
-\begin{itemize}
+\begin{itemize}
\item Discovery and attachment of virtio devices (as described above).
\item Initialization of virtqueues and transport-specific facilities (using
virtio-specific channel commands).
\item Notifications (via hypercall and a combination of I/O interrupts
and indicator bits).
-\end{itemize}
+\end{itemize}
\subsubsection{Channel Commands for Virtio}\label{sec:Virtio Transport Options / Virtio
over channel I/O / Basic Concepts/ Channel Commands for Virtio}
@@ -107,7 +107,7 @@ \subsubsection{Notifications}\label{sec:Virtio Transport Options / Virtio
Host->Guest Notification / Notification via Classic I/O Interrupts} and
\ref{sec:Virtio Transport Options / Virtio over channel I/O / Device
Operation / Host->Guest Notification / Notification via Adapter I/O
-Interrupts} respectively.
+Interrupts} respectively.
Configuration change notifications are done using so-called classic I/O
interrupts. The initialization is described in section \ref{sec:Virtio
@@ -413,7 +413,7 @@ \subsubsection{Setting Up Indicators}\label{sec:Virtio Transport Options / Virti
\begin{itemize}
\item a summary indicator byte covering the virtqueues for one or more
virtio-ccw proxy devices
-\item a set of contigous indicator bits for the virtqueues for a
+\item a set of contiguous indicator bits for the virtqueues for a
virtio-ccw proxy device
\end{itemize}
@@ -563,7 +563,7 @@ \subsubsection{Guest->Host Notification}\label{sec:Virtio Transport Options / Vi
\drivernormative{\paragraph}{Guest->Host Notification}{Virtio Transport Options / Virtio over channel I/O / Device Operation / Guest->Host Notification}
-For each notification, the driver SHOULD use GPR4 to pass the host cookie received in GPR2 from the previous notication.
+For each notification, the driver SHOULD use GPR4 to pass the host cookie received in GPR2 from the previous notification.
\begin{note}
For example:
--
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 prev parent reply other threads:[~2023-02-24 22:22 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 ` Parav Pandit [this message]
2023-02-24 22:22 ` [virtio-dev] [PATCH v5 6/6] transport-ccw: " 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 ` [virtio-dev] " Michael S. Tsirkin
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=20230224222215.339715-7-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