From: Jakub Kicinski <kuba@kernel.org>
To: menglong8.dong@gmail.com
Cc: 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 v3 3/3] net: dropreason: reformat the comment fo skb drop reasons
Date: Wed, 1 Jun 2022 17:42:09 -0700 [thread overview]
Message-ID: <20220601174209.1afdb123@kernel.org> (raw)
In-Reply-To: <20220601065238.1357624-4-imagedong@tencent.com>
The patches LGTM now! net-next is closed until -rc1 is released
so please repost on/after Monday.
> + * en...maybe they should be splited by group?
nit: since we need a repost - I think we can drop this line.
next prev parent reply other threads:[~2022-06-02 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 6:52 [PATCH net-next v3 0/3] reorganize the code of the enum skb_drop_reason menglong8.dong
2022-06-01 6:52 ` [PATCH net-next v3 1/3] net: skb: move enum skb_drop_reason to standalone header file menglong8.dong
2022-06-01 6:52 ` [PATCH net-next v3 2/3] net: skb: use auto-generation to convert skb drop reason to string menglong8.dong
2022-06-01 6:52 ` [PATCH net-next v3 3/3] net: dropreason: reformat the comment fo skb drop reasons menglong8.dong
2022-06-02 0:42 ` Jakub Kicinski [this message]
2022-06-02 1:59 ` Menglong Dong
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=20220601174209.1afdb123@kernel.org \
--to=kuba@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=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).