From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>, <ast@fb.com>,
<daniel@iogearbox.net>
Cc: <andrii@kernel.org>, <kernel-team@fb.com>
Subject: [PATCH v2 bpf-next 0/4] Generate NULL in vmlinux.h
Date: Tue, 16 Mar 2021 20:12:53 -0700 [thread overview]
Message-ID: <20210317031257.846314-1-andrii@kernel.org> (raw)
Generate NULL definition as part of vmlinux.h. This is a pretty common and
unfortunate annoyance that most users of vmlinux.h have to deal with. Patch #2
drops such custom NULL definition in one of the selftests. Patches #3 and #4
make bpftool and selftests compilations stricter by treating warnings as
errors.
v1->v2:
- fix few typos and wrong copy/paste;
- fix #pragma push -> pop.
Andrii Nakryiko (4):
bpftool: generate NULL definition in vmlinux.h
selftests/bpf: drop custom NULL #define in skb_pkt_end selftest
selftests/bpf: treat compilation warnings as errors
bpftool: treat compilation warnings as errors
tools/bpf/bpftool/Makefile | 3 ++-
tools/bpf/bpftool/btf.c | 2 ++
tools/bpf/bpftool/jit_disasm.c | 3 +++
tools/testing/selftests/bpf/Makefile | 4 ++--
tools/testing/selftests/bpf/progs/skb_pkt_end.c | 1 -
5 files changed, 9 insertions(+), 4 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-17 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 3:12 Andrii Nakryiko [this message]
2021-03-17 3:12 ` [PATCH v2 bpf-next 1/4] bpftool: generate NULL definition in vmlinux.h Andrii Nakryiko
2021-03-17 17:36 ` Andrii Nakryiko
2021-03-17 18:15 ` Alexei Starovoitov
2021-03-17 3:12 ` [PATCH v2 bpf-next 2/4] selftests/bpf: drop custom NULL #define in skb_pkt_end selftest Andrii Nakryiko
2021-03-17 3:12 ` [PATCH v2 bpf-next 3/4] selftests/bpf: treat compilation warnings as errors Andrii Nakryiko
2021-03-17 3:12 ` [PATCH v2 bpf-next 4/4] bpftool: " Andrii Nakryiko
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=20210317031257.846314-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).