From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.linux.dev, mst@redhat.com,
cohuck@redhat.com, shahafs@nvidia.com
Subject: Re: [PATCH 3/3] common: editorial: Fix spelling errors
Date: Mon, 9 Sep 2024 16:00:56 +0200 [thread overview]
Message-ID: <Zt7/mFCU0t8JEyU1@fedora> (raw)
In-Reply-To: <20240907174819.778971-4-parav@nvidia.com>
On Sat, Sep 07, 2024 at 08:48:19PM +0300, Parav Pandit wrote:
> Fix spelling errors.
>
> Branch: virtio-1.4
> Fixes: 5f1a8ac61c15 ("admin: introduce virtio admin virtqueues")
> Fixes: 68f66ff7a3d9 ("content: define what an exported object is")
> Fixes: ef16b644cc25 ("content.tex: spec text converted to latex")
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> admin.tex | 2 +-
> content.tex | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/admin.tex b/admin.tex
> index 95054ed..845ca02 100644
> --- a/admin.tex
> +++ b/admin.tex
> @@ -496,7 +496,7 @@ \section{Administration Virtqueues}\label{sec:Basic Facilities of a Virtio Devic
> than one administration virtqueue.
>
> If VIRTIO_F_ADMIN_VQ has been negotiated, an owner device exposes one
> -or more adminstration virtqueues. The number and locations of the
> +or more administration virtqueues. The number and locations of the
> administration virtqueues are exposed by the owner device in a transport
> specific manner.
>
> diff --git a/content.tex b/content.tex
> index 12f9224..c5e7d5a 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -493,7 +493,7 @@ \section{Driver Notifications} \label{sec:Basic Facilities of a Virtio Device /
> \section{Exporting Objects}\label{sec:Basic Facilities of a Virtio Device / Exporting Objects}
>
> When an object created by one virtio device needs to be
> -shared with a seperate virtio device, the first device can
> +shared with a separate virtio device, the first device can
> export the object by generating a UUID which can then
> be passed to the second device to identify the object.
>
> @@ -508,7 +508,7 @@ \section{Exporting Objects}\label{sec:Basic Facilities of a Virtio Device / Expo
> \chapter{General Initialization And Device Operation}\label{sec:General Initialization And Device Operation}
>
> We start with an overview of device initialization, then expand on the
> -details of the device and how each step is preformed. This section
> +details of the device and how each step is performed. This section
> is best read along with the bus-specific section which describes
> how to communicate with the specific device.
>
> --
> 2.34.1
>
>
Reviewed-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
Thanks.
prev parent reply other threads:[~2024-09-09 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 17:48 [PATCH 0/3] editorial: Fix spelling errors Parav Pandit
2024-09-07 17:48 ` [PATCH 1/3] crypto: " Parav Pandit
2024-09-09 14:02 ` Matias Ezequiel Vara Larsen
2024-09-07 17:48 ` [PATCH 2/3] gpu: " Parav Pandit
2024-09-09 14:11 ` Matias Ezequiel Vara Larsen
2024-09-10 16:42 ` Parav Pandit
2024-09-07 17:48 ` [PATCH 3/3] common: " Parav Pandit
2024-09-09 14:00 ` Matias Ezequiel Vara Larsen [this message]
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=Zt7/mFCU0t8JEyU1@fedora \
--to=mvaralar@redhat.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
/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