netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	David Ahern <dsahern@kernel.org>, Shuah Khan <shuah@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stefano Salsano <stefano.salsano@uniroma2.it>,
	Paolo Lungaroni <paolo.lungaroni@uniroma2.it>
Subject: Re: [PATCH net-next 1/2] seg6: fix lenghts typo in a comment
Date: Mon, 30 Jun 2025 17:08:50 +0100	[thread overview]
Message-ID: <20250630160850.GH41770@horms.kernel.org> (raw)
In-Reply-To: <20250629171226.4988-2-andrea.mayer@uniroma2.it>

On Sun, Jun 29, 2025 at 07:12:25PM +0200, Andrea Mayer wrote:
> Fix a typo:
>   lenghts -> length
> 
> The typo has been identified using codespell, and the tool currently
> does not report any additional issues in comments.
> 
> Signed-off-by: Andrea Mayer <andrea.mayer@uniroma2.it>

Thanks,

With this patch in place I see that codespell only flags
false-positives for net/ipv6/seg6_*

Reviewed-by: Simon Horman <horms@kernel.org>

  reply	other threads:[~2025-06-30 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-29 17:12 [PATCH net-next 0/2] seg6: fix typos in comments within the SRv6 subsystem Andrea Mayer
2025-06-29 17:12 ` [PATCH net-next 1/2] seg6: fix lenghts typo in a comment Andrea Mayer
2025-06-30 16:08   ` Simon Horman [this message]
2025-06-29 17:12 ` [PATCH net-next 2/2] selftests: seg6: fix instaces typo in comments Andrea Mayer
2025-06-30 16:09   ` Simon Horman
2025-07-02  2:40 ` [PATCH net-next 0/2] seg6: fix typos in comments within the SRv6 subsystem 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=20250630160850.GH41770@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrea.mayer@uniroma2.it \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paolo.lungaroni@uniroma2.it \
    --cc=shuah@kernel.org \
    --cc=stefano.salsano@uniroma2.it \
    /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).