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 v3 bpf-next 0/2] Provide NULL and KERNEL_VERSION macros in bpf_helpers.h
Date: Wed, 17 Mar 2021 13:05:08 -0700 [thread overview]
Message-ID: <20210317200510.1354627-1-andrii@kernel.org> (raw)
Provide NULL and KERNEL_VERSION macros in bpf_helpers.h. Patch #2 removes such
custom NULL definition from one of the selftests.
v2->v3:
- instead of vmlinux.h, do this in bpf_helpers.h;
- added KERNEL_VERSION, which comes up periodically as well;
- I dropped strict compilation patches for now, because we run into new
warnings (e.g., not checking read() result) in kernel-patches CI, which
I can't even reproduce locally. Also -Wdiscarded-qualifiers pragma for
jit_disasm.c is not supported by Clang, it needs to be
-Wincompatible-pointer-types-discards-qualifiers for Clang; we don't have
to deal with that in this patch set;
v1->v2:
- fix few typos and wrong copy/paste;
- fix #pragma push -> pop.
Andrii Nakryiko (2):
libbpf: provide NULL and KERNEL_VERSION macros in bpf_helpers.h
selftests/bpf: drop custom NULL #define in skb_pkt_end selftest
tools/lib/bpf/bpf_helpers.h | 16 +++++++++++++++-
tools/testing/selftests/bpf/progs/skb_pkt_end.c | 1 -
2 files changed, 15 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-17 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:05 Andrii Nakryiko [this message]
2021-03-17 20:05 ` [PATCH v3 bpf-next 1/2] libbpf: provide NULL and KERNEL_VERSION macros in bpf_helpers.h Andrii Nakryiko
2021-03-17 20:05 ` [PATCH v3 bpf-next 2/2] selftests/bpf: drop custom NULL #define in skb_pkt_end selftest Andrii Nakryiko
2021-03-18 3:28 ` [PATCH v3 bpf-next 0/2] Provide NULL and KERNEL_VERSION macros in bpf_helpers.h Alexei Starovoitov
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=20210317200510.1354627-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).