From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Mayer <andrea.mayer@uniroma2.it>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, horms@kernel.org,
shuah@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stefano.salsano@uniroma2.it,
paolo.lungaroni@uniroma2.it
Subject: Re: [PATCH net-next 0/2] seg6: fix typos in comments within the SRv6 subsystem
Date: Wed, 02 Jul 2025 02:40:24 +0000 [thread overview]
Message-ID: <175142402424.183540.7987068313674190464.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250629171226.4988-1-andrea.mayer@uniroma2.it>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 29 Jun 2025 19:12:24 +0200 you wrote:
> In this patchset, we correct some typos found both in the SRv6 Endpoints
> implementation (i.e., seg6local) and in some SRv6 selftests, using
> codespell.
>
> The patchset is organized as follows:
> Patch 1/2: seg6: fix lenghts typo in a comment
> Patch 2/2: selftests: seg6: fix instaces typo in comments
>
> [...]
Here is the summary with links:
- [net-next,1/2] seg6: fix lenghts typo in a comment
https://git.kernel.org/netdev/net-next/c/db3e2ceab3c7
- [net-next,2/2] selftests: seg6: fix instaces typo in comments
https://git.kernel.org/netdev/net-next/c/3bedaff19bd8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-07-02 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 17:12 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
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 ` patchwork-bot+netdevbpf [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=175142402424.183540.7987068313674190464.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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
all inboxes | Powered by JetHome®