diff options
author | 2023-07-12 16:23:22 +0100 | |
---|---|---|
committer | 2023-07-12 23:50:11 +0200 | |
commit | 0a5550b1165cd60ad6972791eda4a3eb7e347280 (patch) | |
tree | 579977300dcca92326dd34428198464cbe4a329f /arch/x86/net/bpf_jit_comp.c | |
parent | Merge branch 'bpf-mem-cache-free-rcu' (diff) | |
download | linux-0a5550b1165cd60ad6972791eda4a3eb7e347280.tar.gz linux-0a5550b1165cd60ad6972791eda4a3eb7e347280.tar.bz2 linux-0a5550b1165cd60ad6972791eda4a3eb7e347280.zip |
bpftool: Use "fallthrough;" keyword instead of comments
After using "__fallthrough;" in a switch/case block in bpftool's
btf_dumper.c [0], and then turning it into a comment [1] to prevent a
merge conflict in linux-next when the keyword was changed into just
"fallthrough;" [2], we can now drop the comment and use the new keyword,
no underscores.
Also update the other occurrence of "/* fallthrough */" in bpftool.
[0] commit 9fd496848b1c ("bpftool: Support inline annotations when dumping the CFG of a program")
[1] commit 4b7ef71ac977 ("bpftool: Replace "__fallthrough" by a comment to address merge conflict")
[2] commit f7a858bffcdd ("tools: Rename __fallthrough to fallthrough")
Signed-off-by: Quentin Monnet <quentin@isovalent.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/bpf/20230712152322.81758-1-quentin@isovalent.com
Diffstat (limited to 'arch/x86/net/bpf_jit_comp.c')
0 files changed, 0 insertions, 0 deletions