From: "Daniel T. Lee" <danieltimlee@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: [bpf-next v4 0/3] samples/bpf: fix LLVM compilation warning
Date: Sun, 18 Dec 2022 15:14:50 +0900 [thread overview]
Message-ID: <20221218061453.6287-1-danieltimlee@gmail.com> (raw)
Currently, compiling samples/bpf with LLVM emits several warning. They
are only small details, but they do not appear when compiled with GCC.
Detailed compilation command and warning logs can be found from bpf CI.
Daniel T. Lee (3):
samples/bpf: remove unused function with test_lru_dist
samples/bpf: replace meaningless counter with tracex4
samples/bpf: fix uninitialized warning with
test_current_task_under_cgroup
samples/bpf/test_current_task_under_cgroup_user.c | 6 ++++--
samples/bpf/test_lru_dist.c | 5 -----
samples/bpf/tracex4_user.c | 4 ++--
3 files changed, 6 insertions(+), 9 deletions(-)
---
Changes in V2:
- Change the cover letter subject
Changes in V3:
- Fix style problem with the patch
Changes in V4:
- Change the cover letter subject
--
2.34.1
next reply other threads:[~2022-12-18 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 6:14 Daniel T. Lee [this message]
2022-12-18 6:14 ` [bpf-next v4 1/3] samples/bpf: remove unused function with test_lru_dist Daniel T. Lee
2022-12-18 6:14 ` [bpf-next v4 2/3] samples/bpf: replace meaningless counter with tracex4 Daniel T. Lee
2022-12-18 6:14 ` [bpf-next v4 3/3] samples/bpf: fix uninitialized warning with test_current_task_under_cgroup Daniel T. Lee
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=20221218061453.6287-1-danieltimlee@gmail.com \
--to=danieltimlee@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=yhs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox