On Tue, May 23, 2023 at 7:38 AM Daniel Borkmann <daniel@xxxxxxxxxxxxx> wrote:
>
> On 5/23/23 1:29 AM, Andrii Nakryiko wrote:
> [...]
> > diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map
> > index a5aa3a383d69..7a4fe80da360 100644
> > --- a/tools/lib/bpf/libbpf.map
> > +++ b/tools/lib/bpf/libbpf.map
> > @@ -389,5 +389,6 @@ LIBBPF_1.2.0 {
> > bpf_link__update_map;
> > bpf_link_get_info_by_fd;
> > bpf_map_get_info_by_fd;
> > + bpf_obj_pin_opts;
>
> Given 1.2.0 went out [0], shouldn't this go into a new LIBBPF_1.3.0 section?
yep, you are right, this should have gone into a new 1.3.0 sections.
I'll add "starting v1.3 dev cycle" patch into v4 and resend.
>
> > bpf_prog_get_info_by_fd;
> > } LIBBPF_1.1.0;
>
> Thanks,
> Daniel
>
> [0] https://lore.kernel.org/bpf/CAEf4BzYJhzEDHarRGvidhPd-DRtu4VXxnQ=HhOG-LZjkbK-MwQ@xxxxxxxxxxxxxx/
>
