From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/3] selftests/bpf: fix compiler warnings reported in -O2 mode
Date: Fri, 06 Oct 2023 18:20:28 +0000 [thread overview]
Message-ID: <169661642814.9586.15213671983813224846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231004001750.2939898-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 3 Oct 2023 17:17:48 -0700 you wrote:
> Fix a bunch of potentially unitialized variable usage warnings that are
> reported by GCC in -O2 mode. Also silence overzealous stringop-truncation
> class of warnings.
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> ---
> tools/testing/selftests/bpf/Makefile | 4 +++-
> .../selftests/bpf/map_tests/map_in_map_batch_ops.c | 4 ++--
> tools/testing/selftests/bpf/prog_tests/bloom_filter_map.c | 4 ++--
> tools/testing/selftests/bpf/prog_tests/connect_ping.c | 4 ++--
> tools/testing/selftests/bpf/prog_tests/linked_list.c | 2 +-
> tools/testing/selftests/bpf/prog_tests/lwt_helpers.h | 3 ++-
> tools/testing/selftests/bpf/prog_tests/queue_stack_map.c | 2 +-
> tools/testing/selftests/bpf/prog_tests/sockmap_basic.c | 8 ++++----
> tools/testing/selftests/bpf/prog_tests/sockmap_helpers.h | 2 +-
> tools/testing/selftests/bpf/prog_tests/sockmap_listen.c | 4 ++--
> tools/testing/selftests/bpf/prog_tests/xdp_metadata.c | 2 +-
> tools/testing/selftests/bpf/test_loader.c | 4 ++--
> tools/testing/selftests/bpf/xdp_features.c | 4 ++--
> tools/testing/selftests/bpf/xdp_hw_metadata.c | 2 +-
> tools/testing/selftests/bpf/xskxceiver.c | 2 +-
> 15 files changed, 27 insertions(+), 24 deletions(-)
Here is the summary with links:
- [bpf-next,1/3] selftests/bpf: fix compiler warnings reported in -O2 mode
(no matching commit)
- [bpf-next,2/3] selftests/bpf: support building selftests in optimized -O2 mode
https://git.kernel.org/bpf/bpf-next/c/46475cc0dded
- [bpf-next,3/3] selftests/bpf: don't truncate #test/subtest field
https://git.kernel.org/bpf/bpf-next/c/0af3aace5b91
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:[~2023-10-06 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 0:17 [PATCH bpf-next 1/3] selftests/bpf: fix compiler warnings reported in -O2 mode Andrii Nakryiko
2023-10-04 0:17 ` [PATCH bpf-next 2/3] selftests/bpf: support building selftests in optimized " Andrii Nakryiko
2023-10-04 8:27 ` Jiri Olsa
2023-10-04 17:21 ` Andrii Nakryiko
2023-10-05 7:19 ` Jiri Olsa
2023-10-05 9:04 ` Alan Maguire
2023-10-06 17:55 ` Andrii Nakryiko
2023-10-06 17:56 ` Andrii Nakryiko
2023-10-04 0:17 ` [PATCH bpf-next 3/3] selftests/bpf: don't truncate #test/subtest field Andrii Nakryiko
2023-10-05 7:21 ` Jiri Olsa
2023-10-05 7:21 ` [PATCH bpf-next 1/3] selftests/bpf: fix compiler warnings reported in -O2 mode Jiri Olsa
2023-10-06 18:20 ` 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=169661642814.9586.15213671983813224846.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=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
/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