From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: kuba@kernel.org, mathew.j.martineau@linux.intel.com,
matthieu.baerts@tessares.net, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
imagedong@tencent.com
Subject: Re: [PATCH net-next] net: mptcp: fix some spelling mistake in mptcp
Date: Wed, 29 Jun 2022 05:20:13 +0000 [thread overview]
Message-ID: <165648001350.19091.5869614487710926226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220627121626.1595732-1-imagedong@tencent.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 27 Jun 2022 20:16:25 +0800 you wrote:
> From: Menglong Dong <imagedong@tencent.com>
>
> codespell finds some spelling mistake in mptcp:
>
> net/mptcp/subflow.c:1624: interaces ==> interfaces
> net/mptcp/pm_netlink.c:1130: regarless ==> regardless
>
> [...]
Here is the summary with links:
- [net-next] net: mptcp: fix some spelling mistake in mptcp
https://git.kernel.org/netdev/net-next/c/d640516a65d8
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:[~2022-06-29 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 12:16 [PATCH net-next] net: mptcp: fix some spelling mistake in mptcp menglong8.dong
2022-06-27 12:27 ` Matthieu Baerts
2022-06-27 13:49 ` net: mptcp: fix some spelling mistake in mptcp: Tests Results MPTCP CI
2022-06-29 5:20 ` 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=165648001350.19091.5869614487710926226.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=menglong8.dong@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).