From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v2] selftests/bpf: Fix set but not used build errors
Date: Sun, 19 Oct 2025 02:30:18 +0000 [thread overview]
Message-ID: <176084101825.3155740.15331784475261731465.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251018082815.20622-1-yangtiezhu@loongson.cn>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 18 Oct 2025 16:28:15 +0800 you wrote:
> There are some set but not used build errors when compiling bpf selftests
> with the latest upstream mainline GCC, at the beginning add the attribute
> __maybe_unused for the variables, but it is better to just add the option
> -Wno-unused-but-set-variable to CFLAGS in Makefile to disable the errors
> instead of hacking the tests.
>
> tools/testing/selftests/bpf/map_tests/lpm_trie_map_basic_ops.c:229:36:
> error: variable ‘n_matches_after_delete’ set but not used [-Werror=unused-but-set-variable=]
>
> [...]
Here is the summary with links:
- [bpf,v2] selftests/bpf: Fix set but not used build errors
https://git.kernel.org/bpf/bpf-next/c/c67f4ae73798
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-19 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 8:28 [PATCH bpf v2] selftests/bpf: Fix set but not used build errors Tiezhu Yang
2025-10-19 2:30 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=176084101825.3155740.15331784475261731465.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yangtiezhu@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox