selftests/bpf: restructure the Makefile as a layered build

[kernel-patches-daemon-bpf]

Pull request for series with
subject: selftests/bpf: restructure the Makefile as a layered build
version: 7
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503

[kernel-patches-daemon-bpf]

Upstream branch: 5e289c5
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-review-bot]

commit 96dd7c3765aa55b423ff7444415b95a550824e7c
Author: Mykola Lysenko <nickolay.lysenko@gmail.com>

selftests/bpf: drop stale lines, restore two header dependencies

This patch removes dead build rules and dependency entries that no longer
serve any purpose, and restores two header dependencies in working form.

> diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
> index 118a7c356e26c..c7c7f27dd8605 100644
> --- a/tools/testing/selftests/bpf/Makefile
> +++ b/tools/testing/selftests/bpf/Makefile
> @@ -4,9 +4,7 @@ include ../../../scripts/Makefile.arch
>  include ../../../scripts/Makefile.include
>
>  CXX ?= $(CROSS_COMPILE)g++
> -OBJCOPY ?= $(CROSS_COMPILE)objcopy
>
> -CURDIR := $(abspath .)
>  TOOLSDIR := $(abspath ../../..)

This isn't a bug, but would it be worth splitting the OBJCOPY and CURDIR
variable removals into their own small cleanup patch? The subject and the
bulk of the changelog focus on stale build rules and the two restored
header dependencies, while these variable removals are unused/redundant
definitions that get their own paragraph at the end.

[ ... ]

---

AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

In-Reply-To-Subject: selftests/bpf: drop stale lines, restore two header dependencies
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/32662817569

[kernel-patches-daemon-bpf]

Upstream branch: 5e289c5
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-daemon-bpf]

Forwarding comment 5388326408 via email
In-Reply-To: 20260823194241.3415152-3-nickolay.lysenko@gmail.com
Patch: https://patchwork.kernel.org/project/netdevbpf/patch/20260823194241.3415152-3-nickolay.lysenko@gmail.com/

[kernel-patches-review-bot]

commit 79d6c61a930a7bcff9e424734672a09c86fbdcf2
Author: Mykola Lysenko <nickolay.lysenko@gmail.com>

selftests/bpf: move shared build definitions into Makefile.buildvars

This commit moves shared build definitions (tree layout, tool locations,
flag assembly, feature probes, signing key paths, and permissive-mode
helpers) from the main Makefile into a new Makefile.buildvars file so
they can be included by multiple makefiles.

> commit 79d6c61a930a7bcff9e424734672a09c86fbdcf2
> Author: Mykola Lysenko <nickolay.lysenko@gmail.com>
> Date:   Sun Aug 23 12:42:40 2026 -0700
>
>     selftests/bpf: move shared build definitions into Makefile.buildvars
>
>     Move the build definitions a test runner needs - tree layout and
>     tool locations, flag assembly, feature probes, signing key paths, the
>     permissive-mode helpers - into Makefile.buildvars, in their current
>     order, as preparation for building each test runner instance in its
>     own sub-make: the definitions become includable by more than one
>     makefile. No rules or recipes are changed.
>
>     The include sits directly after ../lib.mk, ahead of the
>     ../../../build/Makefile.feature evaluation, so the definitions are in
>     place for everything the top Makefile parses afterwards - in particular
>     the LLVM feature probe captures srctree and PKG_CONFIG from their new
>     location, and the top Makefile's remaining uses of both are all
>     recipe-time expansions. Two evaluation-time changes follow from
>     the new position and a third is made on the way, each commented in
>     place: CFLAGS and LDFLAGS are
>     reassembled around a snapshot taken before lib.mk, keeping the
>     pre-split order;
>     CLANG_SYS_INCLUDES becomes an immediate assignment (its inputs are
>     final by this point, and expanding it forks shells); and the
>     CLANG_HAS_ARENA_ASAN probe now sees CLANG as resolved from
>     LLVM=<suffix-or-path> rather than the bare 'clang' default it saw
>     above the include, while the CLANG_CPUV4 probe, needed before lib.mk,
>     keeps the old behavior.
>
>     BPF_GCC, TEST_KMODS and the knobs the runner never reads (SKIP_*,
>     submake_extras, TEST_KMOD_TARGETS, the VMLINUX_BTF block) stay in the
>     Makefile - the first two are needed before lib.mk is included, where
>     Makefile.buildvars cannot yet be, and reach the runners from there once
>     a later patch adds them: TEST_KMODS exported in the environment, BPF_GCC
>     as the bpf_gcc flavor's compiler parameter. Definitions that reach no
>     runner, directly or as a sub-make parameter, also stay - except
>     HOST_INCLUDE_DIR, which moves with the conditional block it shares
>     with the host build directories - and the four that derive from
>     Makefile.buildvars values sit in a block right after the include.
>
>     Suggested-by: Eduard Zingerman <eddyz87@gmail.com>
>     Assisted-by: Claude:claude-fable-5 shellcheck
>     Signed-off-by: Mykola Lysenko <nickolay.lysenko@gmail.com>

This isn't a bug, but the second paragraph has some lines that look
unfinished mid-paragraph ("place: CFLAGS and LDFLAGS are" at 29
columns, then "pre-split order;" at 16 columns), as if the text was
edited but not rewrapped. Would it help to reflow those lines?

The third paragraph walks through which variables moved and which
stayed ("BPF_GCC, TEST_KMODS and the knobs the runner never reads...
also stay - except HOST_INCLUDE_DIR..."), restating what the diff shows.
The key detail - that BPF_GCC and TEST_KMODS must be defined before
../lib.mk - is there, but it's somewhat buried in the inventory. Would
trimming the list and keeping just the reason make this clearer?

> diff --git a/tools/testing/selftests/bpf/Makefile.buildvars b/tools/testing/selftests/bpf/Makefile.buildvars
> new file mode 100644
> index 0000000000000..dc0be9ee72bc0
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/Makefile.buildvars
> @@ -0,0 +1,184 @@
> +# SPDX-License-Identifier: GPL-2.0
> +#
> +# Shared toolchain, path and flag definitions for the BPF selftests
> +# build, included by both Makefile and Makefile.runner. Definitions
> +# follow the order they had in the Makefile before the split.
> +
> +TOOLSDIR := $(abspath ../../..)

[ ... ]

> +# Before the split these definitions sat above the ../lib.mk include:
> +# they appended to the flags inherited from the environment, and
> +# lib.mk's additions (USERCFLAGS/USERLDFLAGS among them) came last.
> +# This file is parsed after lib.mk at the top level and in its place
> +# in the runner sub-makes, so the same order is rebuilt here. The
> +# includer snapshots the inherited flags in INHERITED_CFLAGS and

This isn't a bug, but the header and several comments are written from
the patch's point of view rather than as documentation of the current
state. The header says definitions "follow the order they had in the
Makefile before the split", and this block starts with "Before the
split these definitions sat above the ../lib.mk include". A reader
arriving later has no "before" to compare against.

The header also says this file is "included by both Makefile and
Makefile.runner", but Makefile.runner doesn't exist until the next
commit. If someone lands here during a bisect, that sentence is
inaccurate.

Would these comments read better stated as the current invariant ("lib.mk
appends to CFLAGS/LDFLAGS; this file's additions must come first, so
the includer snapshots them in INHERITED_*"), and should the header
mention Makefile.runner only once it exists?

---

AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

In-Reply-To-Subject: selftests/bpf: move shared build definitions into Makefile.buildvars
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/32662817569

[kernel-patches-daemon-bpf]

Forwarding comment 5388352519 via email
In-Reply-To: 20260823194241.3415152-9-nickolay.lysenko@gmail.com
Patch: https://patchwork.kernel.org/project/netdevbpf/patch/20260823194241.3415152-9-nickolay.lysenko@gmail.com/

[kernel-patches-review-bot]

commit 2c5b93f3e52b47182259f3354c543be38f34cd63
Author: Mykola Lysenko <nickolay.lysenko@gmail.com>

selftests/bpf: build each test runner instance in its own sub-make

Replace the DEFINE_TEST_RUNNER/DEFINE_TEST_RUNNER_RULES double-expansion
machinery - whose rules never appear in the source as written, are
invisible to make's own debugging facilities, and are easy to break
for one flavor while testing another - with Makefile.runner: one
sub-make invocation per test runner
instance (test_progs, test_progs-no_alu32, test_progs-cpuv4,
test_progs-bpf_gcc, test_maps), each in its own single-flavor namespace
written in plain make - no define/eval layer, no per-flavor guards,
no accumulating vpath directives.

> Replace the DEFINE_TEST_RUNNER/DEFINE_TEST_RUNNER_RULES double-expansion
> machinery - whose rules never appear in the source as written, are
> invisible to make's own debugging facilities, and are easy to break
> for one flavor while testing another - with Makefile.runner: one
> sub-make invocation per test runner
> instance (test_progs, test_progs-no_alu32, test_progs-cpuv4,
> test_progs-bpf_gcc, test_maps), each in its own single-flavor namespace
> written in plain make - no define/eval layer, no per-flavor guards,
> no accumulating vpath directives.
> The main Makefile keeps everything that exists once - tool sub-builds,
> vmlinux.h, signing keys, tests.h generation, standalone binaries and
> the kselftest lib.mk contract - and delegates to the runner through
> explicit per-instance rules.
> The rules for one flavor's BPF objects and skeletons live in
> Makefile.skel, instantiated by the main Makefile for the default
> flavor and by each runner sub-make that builds BPF objects. lib.mk's
> install rule copies the default flavor's BPF objects - the files the
> flat copy of every flavor's objects resolved to before. No file is
> built twice in one build: the main Makefile produces the default
> flavor's artifacts before the unflavored test_progs sub-make runs,
> and each flavored runner writes its own subdirectory plus its binary
> in $(OUTPUT) (the bpftool
> link in $(OUTPUT) is refreshed by both unflavored sub-makes, as
> before).
> The runner instances link userspace objects the main Makefile
> builds once; the
> flavored instances link the shared objects instead of compiling
> their own identical copies.

This isn't a bug, but the wrapping looks unusual here. Several lines
break after only a few words in the middle of a sentence (e.g., "with
Makefile.runner: one / sub-make invocation per test runner / instance"
and "and each flavored runner writes its own subdirectory plus its
binary / in $(OUTPUT) (the bpftool / link in $(OUTPUT) is refreshed").

Could the changelog be reflowed to a consistent width? Kernel changelogs
are conventionally wrapped at around 72-75 columns with blank lines
between paragraphs.

> Smaller behaviour changes that come with the move, for the record:
> the skeleton recipes' build-log lines take the msg helper's format
> and stream, the shared userspace objects log as CC rather than
> EXT-OBJ/LIB-OBJ, and TEST-HDR lines lose their runner tag; the signed
> light-skeleton rule lists the key and certificate it uses as
> prerequisites; the extras copy skips an empty file list and, in
> permissive mode, does not wait for files whose build was skipped;
> $(OUTPUT)/test_maps waits for the same shared prerequisites as the
> other runners; the bare-name convenience targets for the
> linked-skeleton constituents (make linked_funcs1.bpf.o) are gone; the
> .d include no longer special-cases the clean, docs-clean and
> emit_tests goals,
> which a runner sub-make never runs; and the test objects' first-build
> ordering lists only the generated headers the runner itself consumes,
> the rest being built by the main Makefile before any runner starts.

This isn't a bug, but the behaviour changes paragraph is written as one
sentence with roughly ten semicolon-separated clauses spanning about 20
lines. At least two of these are user-visible interface changes (the
bare-name convenience targets like "make linked_funcs1.bpf.o" are gone,
and the .d include no longer special-cases clean/docs-clean/emit_tests)
rather than cosmetic log changes.

Could this be turned into a bulleted list with the interface-affecting
changes called out separately?

> diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
> --- a/tools/testing/selftests/bpf/Makefile
> +++ b/tools/testing/selftests/bpf/Makefile

[ ... ]

> @@ -672,76 +416,109 @@
>  	+$(MAKE) -C libarena libarena_asan.skel.h $(LIBARENA_MAKE_ARGS)
>  endif
>
> -# Define test_progs test runner.
> -TRUNNER_TESTS_DIR := prog_tests
> -TRUNNER_BPF_PROGS_DIR := progs
> -TRUNNER_EXTRA_SOURCES := test_progs.c		\
> -			 cgroup_helpers.c	\
> -			 trace_helpers.c	\
> -			 network_helpers.c	\
> -			 testing_helpers.c	\
> -			 btf_helpers.c		\
> -			 cap_helpers.c		\
> -			 unpriv_helpers.c 	\
> -			 sysctl_helpers.c	\
> -			 netlink_helpers.c	\
> -			 jit_disasm_helpers.c	\
> -			 io_helpers.c		\
> -			 test_loader.c		\
> -			 xsk.c			\
> -			 disasm.c		\
> -			 disasm_helpers.c	\
> -			 json_writer.c 		\
> -			 $(VERIFY_SIG_HDR)		\
> -			 flow_dissector_load.h	\
> -			 ip_check_defrag_frags.h	\
> -			 bpftool_helpers.c	\
> -			 usdt_1.c usdt_2.c	\
> -			 $(LIBARENA_SKEL)	\
> -			 $(LIBARENA_ASAN_SKEL)
> -TRUNNER_LIB_SOURCES := find_bit.c
> -TRUNNER_EXTRA_FILES := $(OUTPUT)/urandom_read				\
> -		       $(OUTPUT)/liburandom_read.so			\
> -		       $(OUTPUT)/xdp_synproxy				\
> -		       $(OUTPUT)/sign-file				\
> -		       $(OUTPUT)/uprobe_multi				\
> -		       $(TEST_KMOD_TARGETS)				\
> -		       ima_setup.sh 					\
> -		       $(VERIFY_SIG_SETUP)				\
> -		       $(wildcard progs/btf_dump_test_case_*.c)		\
> -		       $(wildcard progs/*.bpf.o)
> -TRUNNER_BPF_BUILD_RULE := CLANG_BPF_BUILD_RULE
> -TRUNNER_BPF_CFLAGS := $(BPF_CFLAGS) $(CLANG_CFLAGS) -DENABLE_ATOMICS_TESTS
> -$(eval $(call DEFINE_TEST_RUNNER,test_progs))
> +# Generated test list headers
> +
> +define gen_tests_hdr
> +	$(call msg,TEST-HDR,,$@)
> +	$(Q)(echo '/* Generated header, do not edit */';		\
> +		  sed -n -E 's/^void (serial_)?test_([a-zA-Z0-9_]+)\((void)?\).*/DEFINE_TEST(\2)/p'	\
> +		$(@D)/*.c | sort) > $@
> +endef
> +
> +prog_tests/tests.h: $(wildcard prog_tests/*.c)
> +	$(gen_tests_hdr)
> +
> +map_tests/tests.h: $(wildcard map_tests/*.c)
> +	$(gen_tests_hdr)
> +
> +# Test runner instances, one sub-make each (see Makefile.runner).
>
> -# Define test_progs-no_alu32 test runner.
> -TRUNNER_BPF_BUILD_RULE := CLANG_NOALU32_BPF_BUILD_RULE
> -TRUNNER_BPF_CFLAGS := $(BPF_CFLAGS) $(CLANG_CFLAGS)
> -$(eval $(call DEFINE_TEST_RUNNER,test_progs,no_alu32))
> +# The LLVM feature-probe results and TEST_KMODS are exported
> +# to the runner sub-makes. CC is passed explicitly instead: exporting it
> +# would also leak lib.mk's CC into the libbpf sub-build, which computes
> +# its own. ('export NAME' on an undefined
> +# variable creates an empty one, so these stay below the definitions.)
> +export LLVM_LDLIBS LLVM_LDFLAGS TEST_KMODS
> +export INHERITED_CFLAGS INHERITED_LDFLAGS
>
> -# Define test_progs-cpuv4 test runner.
> +RUNNER_MAKE := $(MAKE) -f Makefile.runner OUTPUT=$(OUTPUT) CC='$(CC)'	\
> +	       CLANG='$(CLANG)'
> +
> +# Everything a runner instance references but does not know how to build.
> +RUNNER_PREREQS := $(INCLUDE_DIR)/vmlinux.h $(BPFOBJ) $(BPFTOOL)		\
> +		  $(TRUNNER_BPFTOOL) $(RESOLVE_BTFIDS)			\
> +		  $(OUTPUT)/veristat					\
> +		  $(VERIFY_SIG_HDR) $(PRIVATE_KEY) $(VERIFICATION_CERT)	\
> +		  $(LIBARENA_SKEL) $(LIBARENA_ASAN_SKEL)		\
> +		  prog_tests/tests.h map_tests/tests.h			\
> +		  $(RUNNER_OBJS)					\
> +		  $(OUTPUT)/urandom_read $(OUTPUT)/liburandom_read.so	\
> +		  $(OUTPUT)/xdp_synproxy $(OUTPUT)/sign-file		\
> +		  $(OUTPUT)/uprobe_multi $(TEST_KMOD_TARGETS)
> +
> +# The main Makefile cannot tell whether $(OUTPUT)/test_progs is stale -
> +# only the runner sub-make knows its full dependency graph. FORCE makes
> +# the delegating rules below always run; their dependents still rebuild
> +# on mtime only.
> +FORCE:
> +
> +# The default flavor's BPF objects and skeletons are consumed here as
> +# well as inside the runner sub-makes: bench, xskxceiver, xdp_* and
> +# test_cpp depend on individual skeletons, and lib.mk's
> +# install rule copies the BPF objects. Instantiate the shared rules
> +# (Makefile.skel) for the default flavor, so those consumers depend on
> +# exactly the files they use; the unflavored runners' delegation rules
> +# below list the whole set as prerequisites, so those sub-makes find the
> +# files this Makefile owns up to date.
> +RDIR := $(OUTPUT)
> +FLAVOR :=
> +BINARY := test_progs
> +BPF_CC := $(CLANG)
> +BPF_CC_MSG := CLNG-BPF
> +BPF_SYS_INCLUDES := $(CLANG_SYS_INCLUDES)
> +BPF_CC_FLAGS := -O2 $(BPF_TARGET_ENDIAN) -mcpu=v3
> +BPF_DEFINES := -DENABLE_ATOMICS_TESTS
> +include Makefile.skel
> +
> +DEFAULT_RUNNER_ARGS := RUNNER=test_progs FLAVOR= TESTS_DIR=prog_tests	\
> +	BPF_CC='$(BPF_CC)' BPF_CC_MSG=$(BPF_CC_MSG)			\
> +	BPF_SYS_INCLUDES='$(BPF_SYS_INCLUDES)'				\
> +	BPF_CC_FLAGS='$(BPF_CC_FLAGS)' BPF_DEFINES=$(BPF_DEFINES)
> +
> +$(OUTPUT)/test_progs: $(RUNNER_PREREQS) $(BPF_OBJS) $(ALL_SKELS) FORCE
> +	+$(Q)$(RUNNER_MAKE) $(DEFAULT_RUNNER_ARGS)
> +
> +$(OUTPUT)/test_progs-no_alu32: $(RUNNER_PREREQS) FORCE
> +	+$(Q)$(RUNNER_MAKE) RUNNER=test_progs FLAVOR=no_alu32 TESTS_DIR=prog_tests \
> +		BPF_CC='$(CLANG)' BPF_CC_MSG=CLNG-BPF BPF_SYS_INCLUDES='$(CLANG_SYS_INCLUDES)'	\
> +		BPF_CC_FLAGS='-O2 $(BPF_TARGET_ENDIAN) -mcpu=v2'
> +
>  ifneq ($(CLANG_CPUV4),)
> -TRUNNER_BPF_BUILD_RULE := CLANG_CPUV4_BPF_BUILD_RULE
> -TRUNNER_BPF_CFLAGS := $(BPF_CFLAGS) $(CLANG_CFLAGS) -DENABLE_ATOMICS_TESTS
> -$(eval $(call DEFINE_TEST_RUNNER,test_progs,cpuv4))
> +$(OUTPUT)/test_progs-cpuv4: $(RUNNER_PREREQS) FORCE
> +	+$(Q)$(RUNNER_MAKE) RUNNER=test_progs FLAVOR=cpuv4 TESTS_DIR=prog_tests \
> +		BPF_CC='$(CLANG)' BPF_CC_MSG=CLNG-BPF BPF_SYS_INCLUDES='$(CLANG_SYS_INCLUDES)'	\
> +		BPF_CC_FLAGS='-O2 $(BPF_TARGET_ENDIAN) -mcpu=v4'		\
> +		BPF_DEFINES=-DENABLE_ATOMICS_TESTS
>  endif

This isn't a bug, but since DEFAULT_RUNNER_ARGS already factors the
clang argument list, would a shared CLANG_RUNNER_ARGS (with just -mcpu=
and BPF_DEFINES varying per flavor) read better than repeating
BPF_CC/BPF_CC_MSG/BPF_SYS_INCLUDES in each of the three clang flavor
recipes?

> diff --git a/tools/testing/selftests/bpf/Makefile.runner b/tools/testing/selftests/bpf/Makefile.runner
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/Makefile.runner
> @@ -0,0 +1,199 @@
> +# SPDX-License-Identifier: GPL-2.0
> +#
> +# Build one BPF test-runner instance: test_progs, one of its flavors
> +# (no_alu32, cpuv4, bpf_gcc), or test_maps.

[ ... ]

> +# Keep in sync with the CFLAGS/LDFLAGS additions in ../lib.mk, in its
> +# order (the selftests include path is spelled from srctree here; lib.mk
> +# spells it from its own directory).
> +ifneq ($(LLVM),)
> +CFLAGS += -Wno-address-of-packed-member
> +CFLAGS += -Wno-gnu-variable-sized-type-not-at-end
> +endif
> +CFLAGS += -D_GNU_SOURCE=
> +CFLAGS += -I$(srctree)/tools/testing/selftests
> +CFLAGS += $(USERCFLAGS)
> +LDFLAGS += $(USERLDFLAGS)

The runner rebuilds the CFLAGS that ../lib.mk used to add, but spells
the selftests include path from $(srctree) instead of lib.mk's
$(top_srcdir). These are not equivalent.

lib.mk derives its path from a realpath, so it is always absolute:

  tools/testing/selftests/lib.mk:61  top_srcdir = $(selfdir)/../../..
  tools/testing/selftests/lib.mk:203 CFLAGS += -I${top_srcdir}/tools/testing/selftests

$(srctree) is exported by the kernel top-level Makefile and is relative
for common cases: '.' for an in-tree build and '..' for a build in a
subdirectory of the source tree. Makefile.buildvars' fallback only fires
when srctree is empty, so it does not normalize a relative value.

The test-object recipe compiles with the working directory changed to
the output directory:

  $(Q)(cd $(@D) && $(CC) -I. $(CFLAGS) -MMD -MT $@ -c $(CURDIR)/$< $(LDLIBS) -o $(@F))

so a relative -I is resolved against $(RDIR), not against the source
tree, and the flag silently names a non-existent directory when the bpf
selftests are built through the kernel top level.

The only include in prog_tests/ or map_tests/ that needs that directory
is prog_tests/test_xsk.h's #include "../kselftest.h", and it is
satisfied earlier by COMMON_CFLAGS' -I$(CURDIR), so this does not break
today. Using an absolute spelling here would keep the runner's
compilation environment identical to the top level's in every
configuration. Was the relative-srctree case considered?

---

AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md

In-Reply-To-Subject: selftests/bpf: build each test runner instance in its own sub-make
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/32662817569

[kernel-patches-daemon-bpf]

Forwarding comment 5388419166 via email
In-Reply-To: 20260823194241.3415152-10-nickolay.lysenko@gmail.com
Patch: https://patchwork.kernel.org/project/netdevbpf/patch/20260823194241.3415152-10-nickolay.lysenko@gmail.com/

[kernel-patches-daemon-bpf]

Upstream branch: 5e289c5
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-daemon-bpf]

Upstream branch: 5e289c5
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-daemon-bpf]

Upstream branch: d83fba2
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-daemon-bpf]

Upstream branch: ce36e38
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-daemon-bpf]

Upstream branch: 05ea1b6
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-daemon-bpf]

Upstream branch: 1555de3
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503
version: 7

[kernel-patches-daemon-bpf]

At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=1150503 expired. Closing PR.