From: Nick Terrell <terrelln@meta.com>
To: Slark Xiao <slark_xiao@163.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lib: zstd: Fix typo 'the the' in comment
Date: Mon, 17 Oct 2022 21:57:24 +0000 [thread overview]
Message-ID: <CA8B85F2-DC40-4D34-88A8-D1B52DF81398@fb.com> (raw)
In-Reply-To: <20220722102426.81464-1-slark_xiao@163.com>
> On Jul 22, 2022, at 3:24 AM, Slark Xiao <slark_xiao@163.com> wrote:
>
> >
> Replace 'the the' with 'the' in the comment.
>
> Signed-off-by: Slark Xiao <slark_xiao@163.com>
Hi Slark, I've already merged another patch which makes this change into my tree,
so I'm dropping this patch.
Best,
Nick Terrell
> ---
> lib/zstd/compress/zstd_compress.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/zstd/compress/zstd_compress.c b/lib/zstd/compress/zstd_compress.c
> index a4e916008b3a..73fff4c60149 100644
> --- a/lib/zstd/compress/zstd_compress.c
> +++ b/lib/zstd/compress/zstd_compress.c
> @@ -4441,7 +4441,7 @@ static size_t ZSTD_validateSequence(U32 offCode, U32 matchLength,
> size_t posInSrc, U32 windowLog, size_t dictSize, U32 minMatch) {
> size_t offsetBound;
> U32 windowSize = 1 << windowLog;
> - /* posInSrc represents the amount of data the the decoder would decode up to this point.
> + /* posInSrc represents the amount of data the decoder would decode up to this point.
> * As long as the amount of data decoded is less than or equal to window size, offsets may be
> * larger than the total length of output decoded in order to reference the dict, even larger than
> * window size. After output surpasses windowSize, we're limited to windowSize offsets again.
> --
> 2.25.1
>
prev parent reply other threads:[~2022-10-17 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 10:24 Slark Xiao
2022-10-17 21:57 ` Nick Terrell [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=CA8B85F2-DC40-4D34-88A8-D1B52DF81398@fb.com \
--to=terrelln@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=slark_xiao@163.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
all inboxes | Powered by JetHome®