From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Claudi <aclaudi@redhat.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org, dsahern@gmail.com
Subject: Re: [PATCH iproute2 v2 0/2] Fix some more typos in docs and comments
Date: Fri, 09 Feb 2024 16:50:30 +0000 [thread overview]
Message-ID: <170749743011.28784.1458264970928294129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1707492043.git.aclaudi@redhat.com>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Fri, 9 Feb 2024 16:25:44 +0100 you wrote:
> Time for some start-of-the-year cleanup :)
>
> Using codespell, fix most of the typos in iproute2 docs and comments,
> except for some false positives. I didn't bother to report a Fixes tag
> for all the typos, but I can do that if needed.
>
> v1 --> v2:
> - rebased and dropped some unnecessary changes.
>
> [...]
Here is the summary with links:
- [iproute2,v2,1/2] treewide: fix typos in various comments
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=9cf6493cab29
- [iproute2,v2,2/2] docs, man: fix some typos
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=3c4712b95d0c
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:[~2024-02-09 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 15:25 [PATCH iproute2 v2 0/2] Fix some more typos in docs and comments Andrea Claudi
2024-02-09 15:25 ` [PATCH iproute2 v2 1/2] treewide: fix typos in various comments Andrea Claudi
2024-02-09 15:25 ` [PATCH iproute2 v2 2/2] docs, man: fix some typos Andrea Claudi
2024-02-09 16:50 ` 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=170749743011.28784.1458264970928294129.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aclaudi@redhat.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.