bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2 bpf-next 00/15] libbpf: remove deprecated APIs
Date: Tue, 28 Jun 2022 20:20:21 +0000	[thread overview]
Message-ID: <165644762109.4858.7045845443300753368.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220627211527.2245459-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Mon, 27 Jun 2022 14:15:12 -0700 you wrote:
> This patch set removes all the deprecated APIs in preparation for 1.0 release.
> It also makes libbpf_set_strict_mode() a no-op (but keeps it to let per-1.0
> applications buildable and dynamically linkable against libbpf 1.0 if they
> were already libbpf-1.0 ready) and starts enforcing all the
> behaviors that were previously opt-in through libbpf_set_strict_mode().
> 
> xsk.{c,h} parts that are now properly provided by libxdp ([0]) are still used
> by xdpxceiver.c in selftest/bpf, so I've moved xsk.{c,h} with barely any
> changes to under selftests/bpf.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,01/15] libbpf: move xsk.{c,h} into selftests/bpf
    https://git.kernel.org/bpf/bpf-next/c/f36600634282
  - [v2,bpf-next,02/15] libbpf: remove deprecated low-level APIs
    https://git.kernel.org/bpf/bpf-next/c/765a34130ea5
  - [v2,bpf-next,03/15] libbpf: remove deprecated XDP APIs
    https://git.kernel.org/bpf/bpf-next/c/53e6af3a761c
  - [v2,bpf-next,04/15] libbpf: remove deprecated probing APIs
    https://git.kernel.org/bpf/bpf-next/c/d320fad217b7
  - [v2,bpf-next,05/15] libbpf: remove deprecated BTF APIs
    https://git.kernel.org/bpf/bpf-next/c/aaf6886d9b53
  - [v2,bpf-next,06/15] libbpf: clean up perfbuf APIs
    https://git.kernel.org/bpf/bpf-next/c/22dd7a58b2e9
  - [v2,bpf-next,07/15] libbpf: remove prog_info_linear APIs
    https://git.kernel.org/bpf/bpf-next/c/9a590538ba4f
  - [v2,bpf-next,08/15] libbpf: remove most other deprecated high-level APIs
    https://git.kernel.org/bpf/bpf-next/c/146bf811f5ac
  - [v2,bpf-next,09/15] libbpf: remove multi-instance and custom private data APIs
    https://git.kernel.org/bpf/bpf-next/c/b4bda502dfa2
  - [v2,bpf-next,10/15] libbpf: cleanup LIBBPF_DEPRECATED_SINCE supporting macros for v0.x
    https://git.kernel.org/bpf/bpf-next/c/a11113a2dcbe
  - [v2,bpf-next,11/15] libbpf: remove internal multi-instance prog support
    https://git.kernel.org/bpf/bpf-next/c/cf90a20db878
  - [v2,bpf-next,12/15] libbpf: clean up SEC() handling
    https://git.kernel.org/bpf/bpf-next/c/450b167fb9be
  - [v2,bpf-next,13/15] selftests/bpf: remove last tests with legacy BPF map definitions
    https://git.kernel.org/bpf/bpf-next/c/31e42721976b
  - [v2,bpf-next,14/15] libbpf: enforce strict libbpf 1.0 behaviors
    https://git.kernel.org/bpf/bpf-next/c/bd054102a8c7
  - [v2,bpf-next,15/15] libbpf: fix up few libbpf.map problems
    https://git.kernel.org/bpf/bpf-next/c/ab9a5a05dc48

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-06-28 20:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 21:15 [PATCH v2 bpf-next 00/15] libbpf: remove deprecated APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 01/15] libbpf: move xsk.{c,h} into selftests/bpf Andrii Nakryiko
2022-06-29  9:41   ` Maciej Fijalkowski
2022-06-29  9:53     ` Daniel Borkmann
2022-06-29  9:55       ` Maciej Fijalkowski
2022-06-27 21:15 ` [PATCH v2 bpf-next 02/15] libbpf: remove deprecated low-level APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 03/15] libbpf: remove deprecated XDP APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 04/15] libbpf: remove deprecated probing APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 05/15] libbpf: remove deprecated BTF APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 06/15] libbpf: clean up perfbuf APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 07/15] libbpf: remove prog_info_linear APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 08/15] libbpf: remove most other deprecated high-level APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 09/15] libbpf: remove multi-instance and custom private data APIs Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 10/15] libbpf: cleanup LIBBPF_DEPRECATED_SINCE supporting macros for v0.x Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 11/15] libbpf: remove internal multi-instance prog support Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 12/15] libbpf: clean up SEC() handling Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 13/15] selftests/bpf: remove last tests with legacy BPF map definitions Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 14/15] libbpf: enforce strict libbpf 1.0 behaviors Andrii Nakryiko
2022-06-27 21:15 ` [PATCH v2 bpf-next 15/15] libbpf: fix up few libbpf.map problems Andrii Nakryiko
2022-06-28 20:20 ` 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=165644762109.4858.7045845443300753368.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;
as well as URLs for NNTP newsgroup(s).