| Message ID | 20241204-resolve_btfids-v3-0-e6a279a74cfd@weissschuh.net (mailing list archive) |
|---|---|
| Headers | show |
| Series | kbuild: propagate CONFIG_WERROR to resolve_btfids | expand |
Hello: This series was applied to bpf/bpf-next.git (master) by Andrii Nakryiko <andrii@kernel.org>: On Wed, 04 Dec 2024 20:37:43 +0100 you wrote: > Use CONFIG_WERROR to also fail on warnings emitted by resolve_btfids. > Allow the CI bots to prevent the introduction of new warnings. > > This series currently depends on > "[PATCH] bpf, lsm: Fix getlsmprop hooks BTF IDs" [0] > > [0] https://lore.kernel.org/lkml/20241123-bpf_lsm_task_getsecid_obj-v1-1-0d0f94649e05@weissschuh.net/ > > [...] Here is the summary with links: - [bpf-next,v3,1/2] tools/resolve_btfids: Add --fatal_warnings option https://git.kernel.org/bpf/bpf-next/c/2fd821354772 - [bpf-next,v3,2/2] kbuild: propagate CONFIG_WERROR to resolve_btfids https://git.kernel.org/bpf/bpf-next/c/0a7a188468c0 You are awesome, thank you!
On Thu, Dec 5, 2024 at 3:30 PM <patchwork-bot+netdevbpf@kernel.org> wrote: > > Hello: > > This series was applied to bpf/bpf-next.git (master) I unlanded this for now. We are waiting for a fix in the bpf tree to make it into bpf-next before we can land this, sorry for the noise. > by Andrii Nakryiko <andrii@kernel.org>: > > On Wed, 04 Dec 2024 20:37:43 +0100 you wrote: > > Use CONFIG_WERROR to also fail on warnings emitted by resolve_btfids. > > Allow the CI bots to prevent the introduction of new warnings. > > > > This series currently depends on > > "[PATCH] bpf, lsm: Fix getlsmprop hooks BTF IDs" [0] > > > > [0] https://lore.kernel.org/lkml/20241123-bpf_lsm_task_getsecid_obj-v1-1-0d0f94649e05@weissschuh.net/ > > > > [...] > > Here is the summary with links: > - [bpf-next,v3,1/2] tools/resolve_btfids: Add --fatal_warnings option > https://git.kernel.org/bpf/bpf-next/c/2fd821354772 > - [bpf-next,v3,2/2] kbuild: propagate CONFIG_WERROR to resolve_btfids > https://git.kernel.org/bpf/bpf-next/c/0a7a188468c0 > > You are awesome, thank you! > -- > Deet-doot-dot, I am a bot. > https://korg.docs.kernel.org/patchwork/pwbot.html > >
Use CONFIG_WERROR to also fail on warnings emitted by resolve_btfids. Allow the CI bots to prevent the introduction of new warnings. This series currently depends on "[PATCH] bpf, lsm: Fix getlsmprop hooks BTF IDs" [0] [0] https://lore.kernel.org/lkml/20241123-bpf_lsm_task_getsecid_obj-v1-1-0d0f94649e05@weissschuh.net/ Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> --- Changes in v3: - Retarget to bpf-next tree - Rename --fatal-warnings to --fatal_warnings for consistency - Link to v2: https://lore.kernel.org/r/20241126-resolve_btfids-v2-0-288c37cb89ee@weissschuh.net Changes in v2: - Avoid uninitialized read of fatal_warnings - Use OPT_BOOLEAN over OPT_INCR - Drop dependency patch, which went in via the kbuild tree - Link to v1: https://lore.kernel.org/r/20241123-resolve_btfids-v1-0-927700b641d1@weissschuh.net --- Thomas Weißschuh (2): tools/resolve_btfids: Add --fatal_warnings option kbuild: propagate CONFIG_WERROR to resolve_btfids scripts/link-vmlinux.sh | 6 +++++- tools/bpf/resolve_btfids/main.c | 12 ++++++++++-- 2 files changed, 15 insertions(+), 3 deletions(-) --- base-commit: e2cf913314b9543f4479788443c7e9009c6c56d8 change-id: 20241123-resolve_btfids-eb95c9b42d00 Best regards,