From: patchwork-bot+netdevbpf@kernel.org
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: kuba@kernel.org, rostedt@goodmis.org, mingo@redhat.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
nhorman@tuxdriver.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
imagedong@tencent.com, dsahern@kernel.org, talalahmad@google.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/3] reorganize the code of the enum skb_drop_reason
Date: Tue, 07 Jun 2022 11:10:13 +0000 [thread overview]
Message-ID: <165460021374.11944.12196215356756517705.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220606022436.331005-1-imagedong@tencent.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 6 Jun 2022 10:24:33 +0800 you wrote:
> From: Menglong Dong <imagedong@tencent.com>
>
> The code of skb_drop_reason is a little wild, let's reorganize them.
> Three things and three patches:
>
> 1) Move the enum 'skb_drop_reason' and related function to the standalone
> header 'dropreason.h', as Jakub Kicinski suggested, as the skb drop
> reasons are getting more and more.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/3] net: skb: move enum skb_drop_reason to standalone header file
https://git.kernel.org/netdev/net-next/c/ff8372a467fa
- [net-next,v4,2/3] net: skb: use auto-generation to convert skb drop reason to string
https://git.kernel.org/netdev/net-next/c/ec43908dd556
- [net-next,v4,3/3] net: dropreason: reformat the comment fo skb drop reasons
https://git.kernel.org/netdev/net-next/c/b160f7270e6d
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-07 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 2:24 [PATCH net-next v4 0/3] reorganize the code of the enum skb_drop_reason menglong8.dong
2022-06-06 2:24 ` [PATCH net-next v4 1/3] net: skb: move enum skb_drop_reason to standalone header file menglong8.dong
2022-06-06 2:24 ` [PATCH net-next v4 2/3] net: skb: use auto-generation to convert skb drop reason to string menglong8.dong
2022-08-25 0:45 ` Eric Dumazet
2022-08-25 1:10 ` Jakub Kicinski
2022-08-25 2:29 ` Menglong Dong
2022-06-06 2:24 ` [PATCH net-next v4 3/3] net: dropreason: reformat the comment fo skb drop reasons menglong8.dong
2022-06-07 11:10 ` 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=165460021374.11944.12196215356756517705.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menglong8.dong@gmail.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=talalahmad@google.com \
--cc=yhs@fb.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).