From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] Re: [PATCH 5/6] transport-mmio: Correct spelling errors
Date: Thu, 16 Feb 2023 15:16:11 +0100 [thread overview]
Message-ID: <87fsb5ae6s.fsf@redhat.com> (raw)
In-Reply-To: <20230203201620.107744-6-parav@nvidia.com>
On Fri, Feb 03 2023, Parav Pandit <parav@nvidia.com> wrote:
> Now that we have individual files, fix reported spelling errors.
>
> While at it, remove extra white space at end of line.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> transport-mmio.tex | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/transport-mmio.tex b/transport-mmio.tex
> index 7f2e0c3..7f4cc15 100644
> --- a/transport-mmio.tex
> +++ b/transport-mmio.tex
> @@ -18,7 +18,7 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
>
> MMIO virtio devices provide a set of memory mapped control
> registers followed by a device-specific configuration space,
> -described in the table~\ref{tab:Virtio Trasport Options / Virtio Over MMIO / MMIO Device Register Layout}.
> +described in the table~\ref{tab:Virtio Transport Options / Virtio Over MMIO / MMIO Device Register Layout}.
>
> All register values are organized as Little Endian.
>
> @@ -32,7 +32,7 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
>
> \begin{longtable}{p{0.2\textwidth}p{0.7\textwidth}}
> \caption {MMIO Device Register Layout}
> - \label{tab:Virtio Trasport Options / Virtio Over MMIO / MMIO Device Register Layout} \\
> + \label{tab:Virtio Transport Options / Virtio Over MMIO / MMIO Device Register Layout} \\
> \hline
> \mmioreg{Name}{Function}{Offset from base}{Direction}{Description}
> \hline
More trailing blanks on those two lines (and also several more in the
other register descriptions) -- maybe fix them all in one go?
---------------------------------------------------------------------
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-16 14: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 ` [PATCH 4/6] transport-pci: Correct spelling errors Parav Pandit
2023-02-03 20:16 ` [PATCH 5/6] transport-mmio: " Parav Pandit
2023-02-16 14:16 ` Cornelia Huck [this message]
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=87fsb5ae6s.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@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 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.