From: "Toke Høiland-Jørgensen" <toke@redhat•com>
To: David Ahern <dsahern@kernel•org>, netdev@vger•kernel.org
Cc: stephen@networkplumber•org, haliu@redhat•com,
David Ahern <dsahern@kernel•org>
Subject: Re: [PATCH iproute2-next 0/3] Address more libbpf deprecations
Date: Sat, 23 Apr 2022 23:35:14 +0200 [thread overview]
Message-ID: <87v8uzbi0d.fsf@toke.dk> (raw)
In-Reply-To: <20220423152300.16201-1-dsahern@kernel.org>
David Ahern <dsahern@kernel•org> writes:
> Another round of changes to handle libbpf deprecations. Compiles are
> clean as of libbpf commit 533c7666eb72 ("Fix downloads formats").
>
> David Ahern (3):
> libbpf: Use bpf_object__load instead of bpf_object__load_xattr
> libbpf: Remove use of bpf_program__set_priv and bpf_program__priv
> libbpf: Remove use of bpf_map_is_offload_neutral
>
> lib/bpf_libbpf.c | 30 +++++++++++++++++-------------
> 1 file changed, 17 insertions(+), 13 deletions(-)
For the series:
Acked-by: Toke Høiland-Jørgensen <toke@redhat•com>
next prev parent reply other threads:[~2022-04-23 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 15:22 [PATCH iproute2-next 0/3] Address more libbpf deprecations David Ahern
2022-04-23 15:22 ` [PATCH iproute2-next 1/3] libbpf: Use bpf_object__load instead of bpf_object__load_xattr David Ahern
2022-04-24 1:56 ` Hangbin Liu
2022-04-24 16:10 ` David Ahern
2022-04-26 2:29 ` Hangbin Liu
2022-04-23 15:22 ` [PATCH iproute2-next 2/3] libbpf: Remove use of bpf_program__set_priv and bpf_program__priv David Ahern
2022-04-23 15:23 ` [PATCH iproute2-next 3/3] libbpf: Remove use of bpf_map_is_offload_neutral David Ahern
2022-04-23 21:35 ` Toke Høiland-Jørgensen [this message]
2022-05-02 21:50 ` [PATCH iproute2-next 0/3] Address more libbpf deprecations patchwork-bot+netdevbpf
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=87v8uzbi0d.fsf@toke.dk \
--to=toke@redhat$(echo .)com \
--cc=dsahern@kernel$(echo .)org \
--cc=haliu@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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