From: Randy Dunlap <rdunlap@infradead.org>
To: Zhang Xiaolei <zxl434815272@gmail.com>,
corbet@lwn.net, ebiggers@kernel.org, andersson@kernel.org,
mathieu.poirier@linaro.org
Cc: ardb@kernel.org, skhan@linuxfoundation.org,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: staging: fix various typos and grammar issues
Date: Thu, 16 Apr 2026 14:10:40 -0700 [thread overview]
Message-ID: <491d3249-1995-4499-9dc2-150e0fd2acef@infradead.org> (raw)
In-Reply-To: <20260416105854.788-1-zxl434815272@gmail.com>
On 4/16/26 3:58 AM, Zhang Xiaolei wrote:
> Fix a few typographical and grammatical issues across several
> staging documentation files to improve readability:
> - crc32.rst: replace "decide in" with "decide on"
> - lzo.rst: replace "independent on" with "independent of"
> - remoteproc.rst: fix word order in dependent clause
> - static-keys.rst: add hyphen to "low-level"
>
> Signed-off-by: Zhang Xiaolei <zxl434815272@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/staging/crc32.rst | 2 +-
> Documentation/staging/lzo.rst | 2 +-
> Documentation/staging/remoteproc.rst | 2 +-
> Documentation/staging/static-keys.rst | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/staging/crc32.rst b/Documentation/staging/crc32.rst
> index 64f3dd430a6c..fc0d9564b99c 100644
> --- a/Documentation/staging/crc32.rst
> +++ b/Documentation/staging/crc32.rst
> @@ -119,7 +119,7 @@ the byte-at-a-time table method, popularized by Dilip V. Sarwate,
> 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.
> +on the correct multiple to subtract, we can shift a byte at a time.
> This produces a 40-bit (rather than a 33-bit) intermediate remainder,
> and the correct multiple of the polynomial to subtract is found using
> a 256-entry lookup table indexed by the high 8 bits.
> diff --git a/Documentation/staging/lzo.rst b/Documentation/staging/lzo.rst
> index f65b51523014..2d48b2667dd2 100644
> --- a/Documentation/staging/lzo.rst
> +++ b/Documentation/staging/lzo.rst
> @@ -75,7 +75,7 @@ Description
> are called under the assumption that a certain number of bytes follow
> because it has already been guaranteed before parsing the instructions.
> They just have to "refill" this credit if they consume extra bytes. This
> - is an implementation design choice independent on the algorithm or
> + is an implementation design choice independent of the algorithm or
> encoding.
>
> Versions
> diff --git a/Documentation/staging/remoteproc.rst b/Documentation/staging/remoteproc.rst
> index 5c226fa076d6..c117b060e76c 100644
> --- a/Documentation/staging/remoteproc.rst
> +++ b/Documentation/staging/remoteproc.rst
> @@ -24,7 +24,7 @@ handlers, and then all rpmsg drivers will then just work
> (for more information about the virtio-based rpmsg bus and its drivers,
> please read Documentation/staging/rpmsg.rst).
> Registration of other types of virtio devices is now also possible. Firmwares
> -just need to publish what kind of virtio devices do they support, and then
> +just need to publish what kind of virtio devices they support, and then
> remoteproc will add those devices. This makes it possible to reuse the
> existing virtio drivers with remote processor backends at a minimal development
> cost.
> diff --git a/Documentation/staging/static-keys.rst b/Documentation/staging/static-keys.rst
> index b0a519f456cf..e8dc3a87c381 100644
> --- a/Documentation/staging/static-keys.rst
> +++ b/Documentation/staging/static-keys.rst
> @@ -90,7 +90,7 @@ out-of-line true branch. Thus, changing branch direction is expensive but
> branch selection is basically 'free'. That is the basic tradeoff of this
> optimization.
>
> -This lowlevel patching mechanism is called 'jump label patching', and it gives
> +This low-level patching mechanism is called 'jump label patching', and it gives
> the basis for the static keys facility.
>
> Static key label API, usage and examples
--
~Randy
next prev parent reply other threads:[~2026-04-16 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 10:58 [PATCH] docs: staging: fix various typos and grammar issues Zhang Xiaolei
2026-04-16 21:10 ` Randy Dunlap [this message]
2026-04-22 14:55 ` Mathieu Poirier
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=491d3249-1995-4499-9dc2-150e0fd2acef@infradead.org \
--to=rdunlap@infradead.org \
--cc=andersson@kernel.org \
--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@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=skhan@linuxfoundation.org \
--cc=zxl434815272@gmail.com \
/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