From: patchwork-bot+netdevbpf@kernel.org
To: Mykola Lysenko <nickolay.lysenko@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
memxor@gmail.com
Subject: Re: [PATCH bpf-next v8 0/9] selftests/bpf: restructure the Makefile as a layered build
Date: Mon, 21 Sep 2026 09:30:07 +0000 [thread overview]
Message-ID: <178998300788.2460388.17148762750813541573.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921075855.2065871-1-nickolay.lysenko@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Mon, 21 Sep 2026 00:58:46 -0700 you wrote:
> The BPF selftests Makefile has grown to ~1,100 lines, with much of the
> complexity concentrated in the DEFINE_TEST_RUNNER double-expansion
> machinery: the per-runner rules are written in $$-escaped make and
> eval'd once per flavor, so the rules that actually run never appear in
> the source and are easy to break for one flavor while testing another.
>
> The series opens with six small stand-alone changes, each usable (or
> droppable) on its own: patch 1 filters headers off the generic link
> rule's command line (gcc tolerates a stray .h there, clang refuses);
> patch 2 drops four stale target-specific lines that name objects nothing
> builds - restoring the two dependencies of value among them in working
> form (flow_dissector_load.h against the binary;
> cgroup_getset_retval_hooks.h by moving it under progs/, where the
> blanket header prerequisite of the BPF object rules covers it) - plus
> three never-referenced linked-skeleton dependency-map entries, a no-op
> CURDIR override and the OBJCOPY definition nothing reads; patch 3
> factors the eleven identical permissive-mode "remove the target, print
> SKIP, report success" recipe tails into a skip_on_fail helper; patch 4
> makes the signing key generation race-free under -j; patch 5 turns the
> verifier/tests.h $(shell)-in-recipe into a regular recipe; patch 6
> derives the bench object list from the sources with a wildcard.
>
> [...]
Here is the summary with links:
- [bpf-next,v8,1/9] selftests/bpf: keep headers off the generic link command line
https://git.kernel.org/bpf/bpf-next/c/75ab33a0a50f
- [bpf-next,v8,2/9] selftests/bpf: drop stale lines, restore two header dependencies
https://git.kernel.org/bpf/bpf-next/c/35ac30e71745
- [bpf-next,v8,3/9] selftests/bpf: factor the permissive-mode skip suffix into a helper
https://git.kernel.org/bpf/bpf-next/c/00c2b472d5dd
- [bpf-next,v8,4/9] selftests/bpf: generate the signing key and certificate once
https://git.kernel.org/bpf/bpf-next/c/73fb8cea7269
- [bpf-next,v8,5/9] selftests/bpf: generate verifier/tests.h in a regular recipe
https://git.kernel.org/bpf/bpf-next/c/7292e0ad85d5
- [bpf-next,v8,6/9] selftests/bpf: derive the bench object list from the sources
https://git.kernel.org/bpf/bpf-next/c/063fa645c723
- [bpf-next,v8,7/9] selftests/bpf: extract BPF skeleton generation into a helper script
https://git.kernel.org/bpf/bpf-next/c/da6cb3aff2cb
- [bpf-next,v8,8/9] selftests/bpf: move shared build definitions into Makefile.buildvars
https://git.kernel.org/bpf/bpf-next/c/ab1d791d0cc4
- [bpf-next,v8,9/9] selftests/bpf: build each test runner instance in its own sub-make
https://git.kernel.org/bpf/bpf-next/c/ef3744f49d98
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:[~2026-09-21 9:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:58 [PATCH bpf-next v8 0/9] selftests/bpf: restructure the Makefile as a layered build Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 1/9] selftests/bpf: keep headers off the generic link command line Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 2/9] selftests/bpf: drop stale lines, restore two header dependencies Mykola Lysenko
2026-09-21 9:06 ` bot+bpf-ci
2026-09-21 9:21 ` Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 3/9] selftests/bpf: factor the permissive-mode skip suffix into a helper Mykola Lysenko
2026-09-21 8:09 ` sashiko-bot
2026-09-21 7:58 ` [PATCH bpf-next v8 4/9] selftests/bpf: generate the signing key and certificate once Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 5/9] selftests/bpf: generate verifier/tests.h in a regular recipe Mykola Lysenko
2026-09-21 9:06 ` bot+bpf-ci
2026-09-21 12:36 ` Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 6/9] selftests/bpf: derive the bench object list from the sources Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 7/9] selftests/bpf: extract BPF skeleton generation into a helper script Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 8/9] selftests/bpf: move shared build definitions into Makefile.buildvars Mykola Lysenko
2026-09-21 7:58 ` [PATCH bpf-next v8 9/9] selftests/bpf: build each test runner instance in its own sub-make Mykola Lysenko
2026-09-21 9:22 ` bot+bpf-ci
2026-09-21 12:08 ` Mykola Lysenko
2026-09-21 9:28 ` [PATCH bpf-next v8 0/9] selftests/bpf: restructure the Makefile as a layered build Kumar Kartikeya Dwivedi
2026-09-21 9: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=178998300788.2460388.17148762750813541573.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=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nickolay.lysenko@gmail.com \
--cc=song@kernel.org \
--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