From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>
Cc: <andrii@kernel.org>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 0/7] libbpf: deprecate some setter and getter APIs
Date: Thu, 20 Jan 2022 16:41:08 -0800 [thread overview]
Message-ID: <20220121004115.3845888-1-andrii@kernel.org> (raw)
Another batch of simple deprecations. One of the last few, hopefully, as we
are getting close to deprecating all the planned APIs/features. See
individual patches for details.
Andrii Nakryiko (7):
libbpf: hide and discourage inconsistently named getters
libbpf: deprecate bpf_map__resize()
libbpf: deprecate bpf_program__is_<type>() and
bpf_program__set_<type>() APIs
bpftool: use preferred setters/getters instead of deprecated ones
selftests/bpf: use preferred setter/getter APIs instead of deprecated
ones
samples/bpf: use preferred getters/setters instead of deprecated ones
perf: use generic bpf_program__set_type() to set BPF prog type
samples/bpf/map_perf_test_user.c | 2 +-
samples/bpf/xdp_redirect_cpu_user.c | 2 +-
samples/bpf/xdp_sample_user.c | 2 +-
samples/bpf/xdp_sample_user.h | 2 +-
tools/bpf/bpftool/gen.c | 2 +-
tools/bpf/bpftool/prog.c | 8 ++---
tools/lib/bpf/btf.h | 5 +--
tools/lib/bpf/libbpf.c | 21 ++++++------
tools/lib/bpf/libbpf.h | 32 +++++++++++++++++--
tools/lib/bpf/libbpf.map | 2 ++
tools/lib/bpf/libbpf_internal.h | 3 ++
tools/lib/bpf/libbpf_legacy.h | 17 ++++++++++
tools/perf/util/bpf-loader.c | 4 +--
.../selftests/bpf/benchs/bench_ringbufs.c | 2 +-
.../selftests/bpf/prog_tests/fexit_bpf2bpf.c | 2 +-
.../prog_tests/get_stackid_cannot_attach.c | 2 +-
.../bpf/prog_tests/stacktrace_build_id_nmi.c | 2 +-
17 files changed, 79 insertions(+), 31 deletions(-)
--
2.30.2
next reply other threads:[~2022-01-21 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 0:41 Andrii Nakryiko [this message]
2022-01-21 0:41 ` [PATCH bpf-next 1/7] libbpf: hide and discourage inconsistently named getters Andrii Nakryiko
2022-01-21 0:41 ` [PATCH bpf-next 2/7] libbpf: deprecate bpf_map__resize() Andrii Nakryiko
2022-01-21 0:43 ` Andrii Nakryiko
2022-01-21 0:41 ` [PATCH bpf-next 3/7] libbpf: deprecate bpf_program__is_<type>() and bpf_program__set_<type>() APIs Andrii Nakryiko
2022-01-21 0:41 ` [PATCH bpf-next 4/7] bpftool: use preferred setters/getters instead of deprecated ones Andrii Nakryiko
2022-01-21 0:41 ` [PATCH bpf-next 5/7] selftests/bpf: use preferred setter/getter APIs " Andrii Nakryiko
2022-01-21 0:41 ` [PATCH bpf-next 6/7] samples/bpf: use preferred getters/setters " Andrii Nakryiko
2022-01-21 0:41 ` [PATCH bpf-next 7/7] perf: use generic bpf_program__set_type() to set BPF prog type 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=20220121004115.3845888-1-andrii@kernel.org \
--to=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.