From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-dev@lists.oasis-open.org, cohuck@redhat.com,
virtio-comment@lists.oasis-open.org, shahafs@nvidia.com
Subject: Re: [PATCH v1 6/6] transport-channelio: Correct spelling errors
Date: Fri, 17 Feb 2023 04:14:49 -0500 [thread overview]
Message-ID: <20230217041419-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230217013008.16062-7-parav@nvidia.com>
On Fri, Feb 17, 2023 at 03:30:08AM +0200, Parav Pandit wrote:
> Now that we have individual files, fix reported spelling errors.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
Why not transport-ccw? We abbreviated pci and mmio didn't we?
> ---
> transport-channelio.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/transport-channelio.tex b/transport-channelio.tex
> index 93401a4..e25a7c1 100644
> --- a/transport-channelio.tex
> +++ b/transport-channelio.tex
> @@ -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
next prev parent reply other threads:[~2023-02-17 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 1:30 [PATCH v1 0/6] Split transport specific files Parav Pandit
2023-02-17 1:30 ` [PATCH v1 1/6] transport-pci: Split PCI transport to its own file Parav Pandit
2023-02-17 1:30 ` [PATCH v1 2/6] transport-mmio: Split MMIO " Parav Pandit
2023-02-17 1:30 ` [PATCH v1 3/6] transport-channelio: Split Channel IO " Parav Pandit
2023-02-17 1:30 ` [PATCH v1 4/6] transport-pci: Correct spelling errors Parav Pandit
2023-02-17 1:30 ` [PATCH v1 5/6] transport-mmio: " Parav Pandit
2023-02-17 10:26 ` Michael S. Tsirkin
2023-02-17 15:59 ` Parav Pandit
2023-02-17 1:30 ` [PATCH v1 6/6] transport-channelio: " Parav Pandit
2023-02-17 9:14 ` Michael S. Tsirkin [this message]
2023-02-17 13:58 ` [virtio-comment] " 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=20230217041419-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.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