[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <tencent_C11060D6C765B08AC1ABE2A801228381B206@qq.com>
Date: Mon, 22 May 2023 11:20:03 +0800
From: Rong Tao <rtoax@...mail.com>
To: ast@...nel.org
Cc: Rong Tao <rongtao@...tc.cn>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Song Liu <song@...nel.org>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
bpf@...r.kernel.org (open list:BPF [GENERAL] (Safe Dynamic Programs and
Tools)), linux-kernel@...r.kernel.org (open list)
Subject: [PATCH bpf-next] samples/bpf: hbm: Fix compile error about fallthrough marking
From: Rong Tao <rongtao@...tc.cn>
commit f7a858bffcdd("tools: Rename __fallthrough to fallthrough") rename
macro __fallthrough to fallthrough, commit 4b7ef71ac977("bpftool: Replace
"__fallthrough" by a comment to address merge conflict") use comments to
replace __fallthrough, here we can use fallthrough directly.
Compiling samples/bpf hits an error related to fallthrough marking:
...
CC samples/bpf/hbm.o
linux/samples/bpf/hbm.c: In function ‘main’:
linux/samples/bpf/hbm.c:501:25: error: ‘__fallthrough’ undeclared
(first use in this function); did you mean ‘fallthrough’?
501 | __fallthrough;
| ^~~~~~~~~~~~~
| fallthrough
Signed-off-by: Rong Tao <rongtao@...tc.cn>
---
samples/bpf/hbm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/samples/bpf/hbm.c b/samples/bpf/hbm.c
index 6448b7826107..7ddf25e9d098 100644
--- a/samples/bpf/hbm.c
+++ b/samples/bpf/hbm.c
@@ -498,7 +498,7 @@ int main(int argc, char **argv)
"Option -%c requires an argument.\n\n",
optopt);
case 'h':
- __fallthrough;
+ fallthrough;
default:
Usage();
return 0;
--
2.39.1
Powered by blists - more mailing lists