From: patchwork-bot+netdevbpf@kernel•org
To: Hou Tao <houtao1@huawei•com>
Cc: ast@kernel•org, kafai@fb•com, yhs@fb•com, daniel@iogearbox•net,
andrii@kernel•org, songliubraving@fb•com,
john.fastabend@gmail•com, netdev@vger•kernel.org,
bpf@vger•kernel.org
Subject: Re: [PATCH bpf-next v5] selftests/bpf: do not export subtest as standalone test
Date: Tue, 08 Feb 2022 20:30:09 +0000 [thread overview]
Message-ID: <164435220906.16710.9125737350953431663.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220208065444.648778-1-houtao1@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox•net>:
On Tue, 8 Feb 2022 14:54:44 +0800 you wrote:
> Two subtests in ksyms_module.c are not qualified as static, so these
> subtests are exported as standalone tests in tests.h and lead to
> confusion for the output of "./test_progs -t ksyms_module".
>
> By using the following command:
>
> grep "^void \(serial_\)\?test_[a-zA-Z0-9_]\+(\(void\)\?)" \
> tools/testing/selftests/bpf/prog_tests/*.c | \
> awk -F : '{print $1}' | sort | uniq -c | awk '$1 != 1'
>
> [...]
Here is the summary with links:
- [bpf-next,v5] selftests/bpf: do not export subtest as standalone test
https://git.kernel.org/bpf/bpf-next/c/5912fcb4bee1
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-02-08 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 6:54 [PATCH bpf-next v5] selftests/bpf: do not export subtest as standalone test Hou Tao
2022-02-08 15:57 ` Yonghong Song
2022-02-08 20:30 ` 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=164435220906.16710.9125737350953431663.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=houtao1@huawei$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kafai@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=songliubraving@fb$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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