From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: idosch@idosch.org, nhorman@tuxdriver.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
dsahern@kernel.org, imagedong@tencent.com
Subject: Re: [PATCH v8 net-next] net: drop_monitor: support drop reason
Date: Thu, 10 Feb 2022 01:30:09 +0000 [thread overview]
Message-ID: <164445660968.21209.6215816253255469230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220209060838.55513-1-imagedong@tencent.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 9 Feb 2022 14:08:38 +0800 you wrote:
> From: Menglong Dong <imagedong@tencent.com>
>
> In the commit c504e5c2f964 ("net: skb: introduce kfree_skb_reason()")
> drop reason is introduced to the tracepoint of kfree_skb. Therefore,
> drop_monitor is able to report the drop reason to users by netlink.
>
> The drop reasons are reported as string to users, which is exactly
> the same as what we do when reporting it to ftrace.
>
> [...]
Here is the summary with links:
- [v8,net-next] net: drop_monitor: support drop reason
https://git.kernel.org/netdev/net-next/c/5cad527d5ffa
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-02-10 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 6:08 [PATCH v8 net-next] net: drop_monitor: support drop reason menglong8.dong
2022-02-09 16:22 ` Ido Schimmel
2022-02-09 21:34 ` David Ahern
2022-02-10 1:30 ` 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=164445660968.21209.6215816253255469230.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=idosch@idosch.org \
--cc=imagedong@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rostedt@goodmis.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).