| Message ID | 20221004131750.2306251-2-roberto.sassu@huaweicloud.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 7a366da2d2ba86316d3ec408f70d19b63916f9ce |
| Headers | show |
| Series | Add _opts variant for bpf_*_get_fd_by_id() | expand |
On Tue, Oct 4, 2022 at 6:18 AM Roberto Sassu <roberto.sassu@huaweicloud.com> wrote: > > From: Roberto Sassu <roberto.sassu@huawei.com> > > Add the missing LIBBPF_0.8.0 at the end of the LIBBPF_1.0.0 declaration, > similarly to other version declarations. > > Cc: stable@vger.kernel.org # 5.19.x there is no need to backport this, libbpf has its own release cycle and it is released from github mirror. And also this doesn't have any effect, this inheritance between versions in .map file is mostly for humans, according [0] (and I checked in practice that it doesn't change anything for libbpf). So it's good to fix, but no need to bother maintainers to backport it to stable branches. [0] https://www.akkadia.org/drepper/dsohowto.pdf > Fixes: e2371b1632b1c ("libbpf: start 1.0 development cycle") > Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com> > --- > tools/lib/bpf/libbpf.map | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map > index c1d6aa7c82b6..04fab9f1fdd7 100644 > --- a/tools/lib/bpf/libbpf.map > +++ b/tools/lib/bpf/libbpf.map > @@ -367,7 +367,7 @@ LIBBPF_1.0.0 { > libbpf_bpf_map_type_str; > libbpf_bpf_prog_type_str; > perf_buffer__buffer; > -}; > +} LIBBPF_0.8.0; > > LIBBPF_1.1.0 { > global: > -- > 2.25.1 >
diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map index c1d6aa7c82b6..04fab9f1fdd7 100644 --- a/tools/lib/bpf/libbpf.map +++ b/tools/lib/bpf/libbpf.map @@ -367,7 +367,7 @@ LIBBPF_1.0.0 { libbpf_bpf_map_type_str; libbpf_bpf_prog_type_str; perf_buffer__buffer; -}; +} LIBBPF_0.8.0; LIBBPF_1.1.0 { global: