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@xxxxxxxxxxxxxx/ Signed-off-by: Thomas Weißschuh <linux@xxxxxxxxxxxxxx> --- 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@xxxxxxxxxxxxxx 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@xxxxxxxxxxxxxx --- 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, -- Thomas Weißschuh <linux@xxxxxxxxxxxxxx>
