-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kbuild: propagate CONFIG_WERROR to resolve_btfids #4701
base: bpf-next_base
Are you sure you want to change the base?
kbuild: propagate CONFIG_WERROR to resolve_btfids #4701
Conversation
Upstream branch: 28eb75e |
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=911973 expired. Closing PR. |
Upstream branch: 27802ca |
48c9d50
to
b9d0a4a
Compare
285d89b
to
f5b233b
Compare
Upstream branch: 27802ca |
b9d0a4a
to
47ac4e4
Compare
f5b233b
to
b69dcbb
Compare
Currently warnings emitted by resolve_btfids are buried in the build log and are slipping into mainline frequently. Add an option to elevate warnings to hard errors so the CI bots can catch any new warnings. Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Acked-by: Jiri Olsa <jolsa@kernel.org>
Upstream branch: c8d02b5 |
Use CONFIG_WERROR to also fail on warnings emitted by resolve_btfids. Allow the CI bots to prevent the introduction of new warnings. Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Acked-by: Jiri Olsa <jolsa@kernel.org>
47ac4e4
to
514bb9c
Compare
Pull request for series with
subject: kbuild: propagate CONFIG_WERROR to resolve_btfids
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=911973