From: sashiko-bot@kernel.org
To: "Mykola Lysenko" <nickolay.lysenko@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [RFC PATCH bpf-next 1/3] selftests/bpf: extract BPF skeleton generation into a helper script
Date: Tue, 21 Jul 2026 17:57:44 +0000 [thread overview]
Message-ID: <20260721175745.228B91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260721174909.8044-2-nickolay.lysenko@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly extracted `gen_bpf_skel.sh` script is not listed as a prerequisite for the skeleton header targets.
--
--- Patch [1]: [RFC PATCH bpf-next 1/3] selftests/bpf: extract BPF skeleton generation into a helper script ---
commit 4513e1c5bea1eb3326128c6ae08f7e1f230247fb
Author: Mykola Lysenko <nickolay.lysenko@gmail.com>
selftests/bpf: extract BPF skeleton generation into a helper script
This commit extracts the duplicate skeleton generation pipeline from the
Makefile into a standalone shell script. This simplifies the rules by
replacing them with calls to gen_bpf_skel.sh using different flags.
> diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
> index b642ee489ea64..e3a27403cd481 100644
> --- a/tools/testing/selftests/bpf/Makefile
> +++ b/tools/testing/selftests/bpf/Makefile
[ ... ]
> @@ -631,81 +631,38 @@ $(TRUNNER_BPF_OBJS): $(TRUNNER_OUTPUT)/%.bpf.o: \
> $$($$<-$2-CFLAGS),$(TRUNNER_BINARY))
>
> $(TRUNNER_BPF_SKELS): %.skel.h: %.bpf.o $(BPFTOOL) | $(TRUNNER_OUTPUT)
[ ... ]
> + $(Q)BPFTOOL=$$(BPFTOOL) ./gen_bpf_skel.sh --tag '$(TRUNNER_BINARY)' \
[Severity: Low]
Should gen_bpf_skel.sh be added as a prerequisite for $(TRUNNER_BPF_SKELS)
and the other skeleton targets?
Without the script in the dependencies list, modifying the script itself
won't trigger a rebuild of the existing .skel.h and .lskel.h files.
This could lead to stale builds during development if the script's logic
is updated.
> + --name $$(notdir $$(<:.bpf.o=)) --infix linked \
> + --skel $$@ --subskel $$(@:.skel.h=.subskel.h) $$< $(if $(PERMISSIVE),|| { \
> + $$(RM) $$@ $$(@:.skel.h=.subskel.h); \
> + printf ' %-12s %s\n' 'SKIP-SKEL' '$$(notdir $$@)' 1>&2; })
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260721174909.8044-1-nickolay.lysenko@gmail.com?part=1
next prev parent reply other threads:[~2026-07-21 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 17:49 [RFC PATCH bpf-next 0/3] selftests/bpf: restructure the Makefile as a layered build Mykola Lysenko
2026-07-21 17:49 ` [RFC PATCH bpf-next 1/3] selftests/bpf: extract BPF skeleton generation into a helper script Mykola Lysenko
2026-07-21 17:57 ` sashiko-bot [this message]
2026-07-21 19:43 ` Mykola Lysenko
2026-07-21 17:49 ` [RFC PATCH bpf-next 2/3] selftests/bpf: move shared build definitions into Makefile.buildvars Mykola Lysenko
2026-07-21 17:49 ` [RFC PATCH bpf-next 3/3] selftests/bpf: build each test runner instance in its own sub-make Mykola Lysenko
2026-07-21 17:58 ` sashiko-bot
2026-07-21 19:43 ` Mykola Lysenko
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=20260721175745.228B91F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=nickolay.lysenko@gmail.com \
--cc=sashiko-reviews@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.