From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/3] Fix few compiler warnings in selftests and libbpf
Date: Wed, 6 Jul 2022 10:11:15 +0200 [thread overview]
Message-ID: <YsVDo7XYPXD4Du++@krava> (raw)
In-Reply-To: <20220705224818.4026623-1-andrii@kernel.org>
On Tue, Jul 05, 2022 at 03:48:15PM -0700, Andrii Nakryiko wrote:
> Few small patches fixing compiler warning issues detected by Coverity or by
> building selftests in -O2 mode.
>
> Andrii Nakryiko (3):
> selftests/bpf: fix bogus uninitialized variable warning
> selftests/bpf: fix few more compiler warnings
> libbpf: remove unnecessary usdt_rel_ip assignments
>
> tools/lib/bpf/usdt.c | 6 ++----
> tools/testing/selftests/bpf/network_helpers.c | 2 +-
> tools/testing/selftests/bpf/prog_tests/kprobe_multi_test.c | 4 ++--
> tools/testing/selftests/bpf/prog_tests/usdt.c | 2 +-
> tools/testing/selftests/bpf/prog_tests/xdp_synproxy.c | 2 +-
> 5 files changed, 7 insertions(+), 9 deletions(-)
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
next prev parent reply other threads:[~2022-07-06 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 22:48 [PATCH bpf-next 0/3] Fix few compiler warnings in selftests and libbpf Andrii Nakryiko
2022-07-05 22:48 ` [PATCH bpf-next 1/3] selftests/bpf: fix bogus uninitialized variable warning Andrii Nakryiko
2022-07-05 22:48 ` [PATCH bpf-next 2/3] selftests/bpf: fix few more compiler warnings Andrii Nakryiko
2022-07-05 22:48 ` [PATCH bpf-next 3/3] libbpf: remove unnecessary usdt_rel_ip assignments Andrii Nakryiko
2022-07-06 6:47 ` [PATCH bpf-next 0/3] Fix few compiler warnings in selftests and libbpf Yonghong Song
2022-07-06 8:11 ` Jiri Olsa [this message]
2022-07-06 14:50 ` patchwork-bot+netdevbpf
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=YsVDo7XYPXD4Du++@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.