From: Martin KaFai Lau <martin.lau@linux.dev>
To: Geliang Tang <geliang@kernel.org>
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>,
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@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] BPF selftests misc fixes
Date: Wed, 10 Jul 2024 12:50:56 -0700 [thread overview]
Message-ID: <31f82582-2eca-475c-a06f-d10615254fb9@linux.dev> (raw)
In-Reply-To: <cover.1720615848.git.tanggeliang@kylinos.cn>
On 7/10/24 6:10 AM, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> v2:
> - only check the first "link" (link_nl) in test_mixed_links().
> - Drop patch 2 in v1.
>
> Resend patch 1 out of "skip ENOTSUPP BPF selftests" set as Eduard
> suggested. Together with another fix for xdp_adjust_tail.
This is not very useful as a cover letter to summarize what has been fixed. I
need to go back to the "skip ENOTSUPP BPF selftests". I beefed it up a little.
I also added the Fixes tag before applying. Please remember to add Fixes tag
next time for bug fixing.
Thanks for the fixes.
prev parent reply other threads:[~2024-07-10 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 13:10 [PATCH bpf-next v2 0/2] BPF selftests misc fixes Geliang Tang
2024-07-10 13:10 ` [PATCH bpf-next v2 1/2] selftests/bpf: Null checks for links in bpf_tcp_ca Geliang Tang
2024-07-10 13:10 ` [PATCH bpf-next v2 2/2] selftests/bpf: Close obj in error path in xdp_adjust_tail Geliang Tang
2024-07-10 19:50 ` [PATCH bpf-next v2 0/2] BPF selftests misc fixes patchwork-bot+netdevbpf
2024-07-10 19:50 ` Martin KaFai Lau [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=31f82582-2eca-475c-a06f-d10615254fb9@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=geliang@kernel.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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