From: Geliang Tang <geliang@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Mykola Lysenko <mykolal@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Geliang Tang <tanggeliang@kylinos.cn>, bpf <bpf@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH bpf-next 00/15] use network helpers, part 11
Date: Wed, 24 Jul 2024 10:07:30 +0800 [thread overview]
Message-ID: <4b1aace7d5dcc0dbc348df568f12d6aba1fa9ddb.camel@kernel.org> (raw)
In-Reply-To: <CAADnVQKHHy92a62vRue44asXqw=OoWwyzg0_g0sbgaK+xbP6Xg@mail.gmail.com>
Hi Alexei,
On Tue, 2024-07-23 at 17:04 -0700, Alexei Starovoitov wrote:
> I strongly suggest you invest just as much time
> in reviewing other people's patches as sending yours
> or they will all be automatically rejected.
Thanks for your reminder. I didn't know that our community has such a
rule. I will try to reduce the number of iterations of my patches and
the number of my emails sent to our community.
I am very willing to review other people's patches, but I am only
familiar with "BPF [SELFTESTS]" module. If possible, I would like to
add myself (Geliang Tang <geliang@kernel.org>) as a reviewer of this
module in MAINTAINERS so that I can receive emails of new patches for
reviewing. Or please add this for me.
Thanks,
-Geliang
next prev parent reply other threads:[~2024-07-24 2:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 22:22 [PATCH bpf-next 00/15] use network helpers, part 11 Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 01/15] selftests/bpf: Use start_server_str in skc_to_unix_sock Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 02/15] selftests/bpf: AF_PACKET support for make_sockaddr Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 03/15] selftests/bpf: Use start_server_str in lwt_redirect Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 04/15] selftests/bpf: Add send_to_fd_opts helper Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 05/15] selftests/bpf: Add send_to_addr_str helper Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 06/15] selftests/bpf: Use send_to_addr_str in xdp_bonding Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 07/15] selftests/bpf: AF_ALG support for make_sockaddr Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 08/15] selftests/bpf: Add nolisten for network_helper_opts Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 09/15] selftests/bpf: Use start_server_str in crypto_sanity Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 10/15] selftests/bpf: AF_VSOCK support for make_sockaddr Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 11/15] selftests/bpf: Add loopback_addr_str helper Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 12/15] selftests/bpf: Use make_sockaddr in sockmap_helpers Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 13/15] selftests/bpf: Check listen support for start_server_addr Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 14/15] selftests/bpf: Clear type bits " Geliang Tang
2024-07-23 22:22 ` [PATCH bpf-next 15/15] selftests/bpf: Use start_server_str in sockmap_helpers Geliang Tang
2024-07-24 0:04 ` [PATCH bpf-next 00/15] use network helpers, part 11 Alexei Starovoitov
2024-07-24 2:07 ` Geliang Tang [this message]
2024-07-24 2:43 ` Alexei Starovoitov
2024-07-24 2:54 ` Geliang Tang
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=4b1aace7d5dcc0dbc348df568f12d6aba1fa9ddb.camel@kernel.org \
--to=geliang@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tanggeliang@kylinos.cn \
--cc=yonghong.song@linux.dev \
/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