From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
rostedt@goodmis.org, mingo@redhat.com, xeb@mail.ru,
davem@davemloft.net, yoshfuji@linux-ipv6.org,
imagedong@tencent.com, edumazet@google.com, kafai@fb.com,
talalahmad@google.com, keescook@chromium.org, alobakin@pm.me,
flyingpeng@tencent.com, mengensun@tencent.com,
dongli.zhang@oracle.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, benbjiang@tencent.com
Subject: Re: [PATCH RESEND net-next v5 0/4] net: icmp: add skb drop reasons to icmp
Date: Mon, 11 Apr 2022 09:50:12 +0000 [thread overview]
Message-ID: <164967061237.14330.9593328118973073943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220407062052.15907-1-imagedong@tencent.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 7 Apr 2022 14:20:48 +0800 you wrote:
> From: Menglong Dong <imagedong@tencent.com>
>
> In the commit c504e5c2f964 ("net: skb: introduce kfree_skb_reason()"),
> we added the support of reporting the reasons of skb drops to kfree_skb
> tracepoint. And in this series patches, reasons for skb drops are added
> to ICMP protocol.
>
> [...]
Here is the summary with links:
- [RESEND,net-next,v5,1/4] net: sock: introduce sock_queue_rcv_skb_reason()
https://git.kernel.org/netdev/net-next/c/c1b8a56755ee
- [RESEND,net-next,v5,2/4] net: skb: rename SKB_DROP_REASON_PTYPE_ABSENT
https://git.kernel.org/netdev/net-next/c/9f8ed577c288
- [RESEND,net-next,v5,3/4] net: icmp: introduce __ping_queue_rcv_skb() to report drop reasons
https://git.kernel.org/netdev/net-next/c/41a95a00ebef
- [RESEND,net-next,v5,4/4] net: icmp: add skb drop reasons to icmp protocol
https://git.kernel.org/netdev/net-next/c/b384c95a861e
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-04-11 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 6:20 [PATCH RESEND net-next v5 0/4] net: icmp: add skb drop reasons to icmp menglong8.dong
2022-04-07 6:20 ` [PATCH RESEND net-next v5 1/4] net: sock: introduce sock_queue_rcv_skb_reason() menglong8.dong
2022-04-09 3:49 ` David Ahern
2022-04-07 6:20 ` [PATCH RESEND net-next v5 2/4] net: skb: rename SKB_DROP_REASON_PTYPE_ABSENT menglong8.dong
2022-04-09 3:50 ` David Ahern
2022-04-07 6:20 ` [PATCH RESEND net-next v5 3/4] net: icmp: introduce __ping_queue_rcv_skb() to report drop reasons menglong8.dong
2022-04-09 4:05 ` David Ahern
2022-04-07 6:20 ` [PATCH RESEND net-next v5 4/4] net: icmp: add skb drop reasons to icmp protocol menglong8.dong
2022-04-09 4:17 ` David Ahern
2022-04-11 9: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=164967061237.14330.9593328118973073943.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alobakin@pm.me \
--cc=benbjiang@tencent.com \
--cc=davem@davemloft.net \
--cc=dongli.zhang@oracle.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=flyingpeng@tencent.com \
--cc=imagedong@tencent.com \
--cc=kafai@fb.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mengensun@tencent.com \
--cc=menglong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=talalahmad@google.com \
--cc=xeb@mail.ru \
--cc=yoshfuji@linux-ipv6.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.