From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>, <cohuck@redhat.com>
Cc: <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH 2/3] gpu: editorial: Fix spelling errors
Date: Sat, 7 Sep 2024 20:48:18 +0300 [thread overview]
Message-ID: <20240907174819.778971-3-parav@nvidia.com> (raw)
In-Reply-To: <20240907174819.778971-1-parav@nvidia.com>
Fix spelling errors.
Branch: virtio-1.4
Fixes: fed64230bf31 ("Add virtio gpu device specification.")
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
device-types/gpu/description.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/device-types/gpu/description.tex b/device-types/gpu/description.tex
index 66e4873..ba4ea76 100644
--- a/device-types/gpu/description.tex
+++ b/device-types/gpu/description.tex
@@ -166,7 +166,7 @@ \subsubsection{Device Operation: Multihead setup}
\devicenormative{\subsubsection}{Device Operation: Command lifecycle and fencing}{Device Types / GPU Device / Device Operation / Device Operation: Command lifecycle and fencing}
-The device MAY process controlq commands asyncronously and return them
+The device MAY process controlq commands asynchronously and return them
to the driver before the processing is complete. If the driver needs
to know when the processing is finished it can set the
VIRTIO_GPU_FLAG_FENCE flag in the request. The device MUST finish the
@@ -345,7 +345,7 @@ \subsubsection{Device Operation: controlq}\label{sec:Device Types / GPU Device /
display).
The \field{enabled} field is set when the user enabled the display.
-It is roughly the same as the connected state of a phyiscal display
+It is roughly the same as the connected state of a physical display
connector.
\item[VIRTIO_GPU_CMD_GET_EDID] Retrieve the EDID data for a given
--
2.34.1
next prev parent reply other threads:[~2024-09-07 17:48 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 ` Parav Pandit [this message]
2024-09-09 14:11 ` [PATCH 2/3] gpu: " 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
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=20240907174819.778971-3-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.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