From: Rakuram Eswaran <rakuram.e96@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: linux-doc@vger.kernel.org, ardb@kernel.org, ebiggers@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
rakuram.e96@gmail.com
Subject: [PATCH] Documentation/staging: Fix typo and incorrect citation in crc32.rst
Date: Wed, 20 Aug 2025 21:56:13 +0530 [thread overview]
Message-ID: <20250820162615.6942-1-rakuram.e96@gmail.com> (raw)
In Documentation/staging/crc32.rst, below errors have been corrected:
1. Line 37: from "to being" to "to bring"
2. Line 119: Incorrect citation date:
It must be August 1988 instead of August 1998
Signed-off-by: Rakuram Eswaran <rakuram.e96@gmail.com>
---
Documentation/staging/crc32.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/staging/crc32.rst b/Documentation/staging/crc32.rst
index 7542220967cb..64f3dd430a6c 100644
--- a/Documentation/staging/crc32.rst
+++ b/Documentation/staging/crc32.rst
@@ -34,7 +34,7 @@ do it in the right order, matching the endianness.
Just like with ordinary division, you proceed one digit (bit) at a time.
Each step of the division you take one more digit (bit) of the dividend
and append it to the current remainder. Then you figure out the
-appropriate multiple of the divisor to subtract to being the remainder
+appropriate multiple of the divisor to subtract to bring the remainder
back into range. In binary, this is easy - it has to be either 0 or 1,
and to make the XOR cancel, it's just a copy of bit 32 of the remainder.
@@ -116,7 +116,7 @@ for any fractional bytes at the end.
To reduce the number of conditional branches, software commonly uses
the byte-at-a-time table method, popularized by Dilip V. Sarwate,
"Computation of Cyclic Redundancy Checks via Table Look-Up", Comm. ACM
-v.31 no.8 (August 1998) p. 1008-1013.
+v.31 no.8 (August 1988) p. 1008-1013.
Here, rather than just shifting one bit of the remainder to decide
in the correct multiple to subtract, we can shift a byte at a time.
--
2.43.0
next reply other threads:[~2025-08-20 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 16:26 Rakuram Eswaran [this message]
2025-08-21 3:59 ` [PATCH] Documentation/staging: Fix typo and incorrect citation in crc32.rst Eric Biggers
2025-08-23 9:18 ` Rakuram Eswaran
2025-08-24 2:36 ` Eric Biggers
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=20250820162615.6942-1-rakuram.e96@gmail.com \
--to=rakuram.e96@gmail.com \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).