From: Yanteng Si <si.yanteng@linux.dev>
To: WangYuli <wangyuli@uniontech.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, tom@herbertland.com,
zhanjun@uniontech.com, niecheng1@uniontech.com,
guanwentao@uniontech.com, Sourcery AI <hello@sourcery.ai>
Subject: Re: [PATCH] docs: networking: strparser: Fix a typo
Date: Tue, 18 Mar 2025 17:12:36 +0800 [thread overview]
Message-ID: <0b152abf-f294-4707-9f3f-4b533eff15e7@linux.dev> (raw)
In-Reply-To: <A43BEA49ED5CC6E5+20250318074656.644391-1-wangyuli@uniontech.com>
在 3/18/25 3:46 PM, WangYuli 写道:
> The context indicates that 'than' is the correct word instead of 'then',
> as a comparison is being performed.
>
> Given that 'then' is also a valid English word, checkpatch.pl wouldn't
> have picked up on this spelling error.
>
> This typo was caught by AI during code review.
>
> Fixes: adcce4d5dd46 ("strparser: Documentation")
> Reported-by: Sourcery AI <hello@sourcery.ai>
> Suggested-by: Wentao Guan <guanwentao@uniontech.com>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
Reviewed-by: Yanteng Si <si.yanteng@linux.dev>
Thanks,
Yanteng
> ---
> Documentation/networking/strparser.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/strparser.rst b/Documentation/networking/strparser.rst
> index 7f623d1db72a..8dc6bb04c710 100644
> --- a/Documentation/networking/strparser.rst
> +++ b/Documentation/networking/strparser.rst
> @@ -180,7 +180,7 @@ There are seven callbacks:
> struct contains two fields: offset and full_len. Offset is
> where the message starts in the skb, and full_len is the
> the length of the message. skb->len - offset may be greater
> - then full_len since strparser does not trim the skb.
> + than full_len since strparser does not trim the skb.
>
> ::
>
next prev parent reply other threads:[~2025-03-18 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:46 [PATCH] docs: networking: strparser: Fix a typo WangYuli
2025-03-18 9:12 ` Yanteng Si [this message]
2025-03-24 19:20 ` patchwork-bot+netdevbpf
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=0b152abf-f294-4707-9f3f-4b533eff15e7@linux.dev \
--to=si.yanteng@linux.dev \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guanwentao@uniontech.com \
--cc=hello@sourcery.ai \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niecheng1@uniontech.com \
--cc=pabeni@redhat.com \
--cc=tom@herbertland.com \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.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