From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, idosch@idosch.org, jiri@nvidia.com,
pablo@netfilter.org, kadlec@netfilter.org, fw@strlen.de,
johannes@sipsolutions.net, ecree.xilinx@gmail.com,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH net-next] netlink: fix spelling mistake in dump size assert
Date: Wed, 25 Jan 2023 01:00:16 +0000 [thread overview]
Message-ID: <167460841619.24500.5551422169194789078.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123222224.732338-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 23 Jan 2023 14:22:24 -0800 you wrote:
> Commit 2c7bc10d0f7b ("netlink: add macro for checking dump ctx size")
> misspelled the name of the assert as asset, missing an R.
>
> Reported-by: Ido Schimmel <idosch@idosch.org>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: jiri@nvidia.com
> CC: pablo@netfilter.org
> CC: kadlec@netfilter.org
> CC: fw@strlen.de
> CC: johannes@sipsolutions.net
> CC: ecree.xilinx@gmail.com
> CC: netfilter-devel@vger.kernel.org
> CC: coreteam@netfilter.org
>
> [...]
Here is the summary with links:
- [net-next] netlink: fix spelling mistake in dump size assert
https://git.kernel.org/netdev/net-next/c/ec8f7d495b3d
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:[~2023-01-25 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 22:22 [PATCH net-next] netlink: fix spelling mistake in dump size assert Jakub Kicinski
2023-01-24 7:37 ` Ido Schimmel
2023-01-25 1:00 ` 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=167460841619.24500.5551422169194789078.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=idosch@idosch.org \
--cc=jiri@nvidia.com \
--cc=johannes@sipsolutions.net \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 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).