[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220328192103.4df73760@kernel.org>
Date: Mon, 28 Mar 2022 19:21:03 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: menglong8.dong@...il.com
Cc: dsahern@...nel.org, pabeni@...hat.com, rostedt@...dmis.org,
mingo@...hat.com, xeb@...l.ru, davem@...emloft.net,
yoshfuji@...ux-ipv6.org, imagedong@...cent.com,
edumazet@...gle.com, kafai@...com, talalahmad@...gle.com,
keescook@...omium.org, alobakin@...me, flyingpeng@...cent.com,
mengensun@...cent.com, dongli.zhang@...cle.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
benbjiang@...cent.com
Subject: Re: [PATCH net-next v5 0/4] net: icmp: add skb drop reasons to icmp
On Mon, 28 Mar 2022 12:27:33 +0800 menglong8.dong@...il.com wrote:
> From: Menglong Dong <imagedong@...cent.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.
# Form letter - net-next is closed
We have already sent the networking pull request for 5.18
and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after 5.18-rc1 is cut.
RFC patches sent for review only are obviously welcome at any time.
Powered by blists - more mailing lists