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 1/3] crypto: editorial: Fix spelling errors
Date: Sat, 7 Sep 2024 20:48:17 +0300 [thread overview]
Message-ID: <20240907174819.778971-2-parav@nvidia.com> (raw)
In-Reply-To: <20240907174819.778971-1-parav@nvidia.com>
Fix spelling errors.
Branch: virtio-1.4
Fixes: a385dd3366a2 ("virtio-crypto: Add virtio crypto device specification")
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
device-types/crypto/description.tex | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/device-types/crypto/description.tex b/device-types/crypto/description.tex
index 5705e26..e053cc7 100644
--- a/device-types/crypto/description.tex
+++ b/device-types/crypto/description.tex
@@ -424,11 +424,11 @@ \subsubsection{Control Virtqueue}\label{sec:Device Types / Crypto Device / Devic
\field{header} is a general header (see above).
-\field{op_flf} is the opcode (in \field{header}) specific fixed-length paramenters.
+\field{op_flf} is the opcode (in \field{header}) specific fixed-length parameters.
\field{flf_len} depends on the VIRTIO_CRYPTO_F_REVISION_1 feature bit (see below).
-\field{op_vlf} is the opcode (in \field{header}) specific variable-length paramenters.
+\field{op_vlf} is the opcode (in \field{header}) specific variable-length parameters.
\field{vlf_len} is the size of the specific structure used.
\begin{note}
@@ -509,7 +509,7 @@ \subsubsection{Control Virtqueue}\label{sec:Device Types / Crypto Device / Devic
\subparagraph{Session operation: HASH session}\label{sec:Device Types / Crypto Device / Device
Operation / Control Virtqueue / Session operation / Session operation: HASH session}
-The fixed-length paramenters of HASH session requests is as follows:
+The fixed-length parameters of HASH session requests is as follows:
\begin{lstlisting}
struct virtio_crypto_hash_create_session_flf {
@@ -1386,7 +1386,7 @@ \subsubsection{Symmetric algorithms Operation}\label{sec:Device Types / Crypto D
\end{itemize*}
The length of \field{op_type_flf} is fixed to 40 bytes, the data of unused
-part (if has) will be ingored.
+part (if has) will be ignored.
\field{op_type_vlf} is the \field{op_type} specific parameters, it MUST starts
with or be one of the following structures:
@@ -1536,7 +1536,7 @@ \subsubsection{Symmetric algorithms Operation}\label{sec:Device Types / Crypto D
\end{itemize*}
The length of \field{op_type_flf} is fixed to 72 bytes, the data of unused
-part (if has) will be ingored.
+part (if has) will be ignored.
\field{op_type_vlf} is the \field{op_type} specific parameters, it MUST starts
with or be one of the following structures:
--
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 ` Parav Pandit [this message]
2024-09-09 14:02 ` [PATCH 1/3] crypto: " 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
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-2-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