From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/6] Clean up leftover uses of deprecated APIs
Date: Thu, 03 Feb 2022 15:40:10 +0000 [thread overview]
Message-ID: <164390281054.30354.12360708187607455235.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220202225916.3313522-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 2 Feb 2022 14:59:10 -0800 you wrote:
> Clean up remaining missed uses of deprecated libbpf APIs across samples/bpf,
> selftests/bpf, libbpf, and bpftool.
>
> Also fix uninit variable warning in bpftool.
>
> Andrii Nakryiko (6):
> libbpf: stop using deprecated bpf_map__is_offload_neutral()
> bpftool: stop supporting BPF offload-enabled feature probing
> bpftool: fix uninit variable compilation warning
> selftests/bpf: remove usage of deprecated feature probing APIs
> selftests/bpf: redo the switch to new libbpf XDP APIs
> samples/bpf: get rid of bpf_prog_load_xattr() use
>
> [...]
Here is the summary with links:
- [bpf-next,1/6] libbpf: stop using deprecated bpf_map__is_offload_neutral()
https://git.kernel.org/bpf/bpf-next/c/a5dd9589f0ab
- [bpf-next,2/6] bpftool: stop supporting BPF offload-enabled feature probing
https://git.kernel.org/bpf/bpf-next/c/1a56c18e6c2e
- [bpf-next,3/6] bpftool: fix uninit variable compilation warning
https://git.kernel.org/bpf/bpf-next/c/a9a8ac592e47
- [bpf-next,4/6] selftests/bpf: remove usage of deprecated feature probing APIs
https://git.kernel.org/bpf/bpf-next/c/32e608f82946
- [bpf-next,5/6] selftests/bpf: redo the switch to new libbpf XDP APIs
https://git.kernel.org/bpf/bpf-next/c/e4e284a8c0d9
- [bpf-next,6/6] samples/bpf: get rid of bpf_prog_load_xattr() use
https://git.kernel.org/bpf/bpf-next/c/1e4edb6d8c4f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-03 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 22:59 [PATCH bpf-next 0/6] Clean up leftover uses of deprecated APIs Andrii Nakryiko
2022-02-02 22:59 ` [PATCH bpf-next 1/6] libbpf: stop using deprecated bpf_map__is_offload_neutral() Andrii Nakryiko
2022-02-02 22:59 ` [PATCH bpf-next 2/6] bpftool: stop supporting BPF offload-enabled feature probing Andrii Nakryiko
2022-02-03 10:24 ` Quentin Monnet
2022-02-16 10:37 ` Niklas Söderlund
2022-02-16 11:47 ` Quentin Monnet
2022-02-16 15:40 ` Niklas Söderlund
2022-02-02 22:59 ` [PATCH bpf-next 3/6] bpftool: fix uninit variable compilation warning Andrii Nakryiko
2022-02-02 22:59 ` [PATCH bpf-next 4/6] selftests/bpf: remove usage of deprecated feature probing APIs Andrii Nakryiko
2022-02-02 22:59 ` [PATCH bpf-next 5/6] selftests/bpf: redo the switch to new libbpf XDP APIs Andrii Nakryiko
2022-02-02 22:59 ` [PATCH bpf-next 6/6] samples/bpf: get rid of bpf_prog_load_xattr() use Andrii Nakryiko
2022-02-03 10:25 ` [PATCH bpf-next 0/6] Clean up leftover uses of deprecated APIs Quentin Monnet
2022-02-03 15:40 ` patchwork-bot+netdevbpf [this message]
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=164390281054.30354.12360708187607455235.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox