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 bpf-next 0/7] Improve set_attach_target() and deprecate open_opts.attach_prog_fd
Date: Fri, 17 Sep 2021 16:10:08 +0000	[thread overview]
Message-ID: <163189500885.20217.13882482710541336384.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210916015836.1248906-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (refs/heads/master):

On Wed, 15 Sep 2021 18:58:29 -0700 you wrote:
> This patch set deprecates bpf_object_open_opts.attach_prog_fd (in libbpf 0.7+)
> by extending bpf_program__set_attach_target() to support some more flexible
> scenarios. Existing fexit_bpf2bpf selftest is updated accordingly to not use
> deprecated APIs.
> 
> While at it, also deprecate no-op relaxed_core_relocs option (they are always
> "relaxed").
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/7] libbpf: use pre-setup sec_def in libbpf_find_attach_btf_id()
    https://git.kernel.org/bpf/bpf-next/c/f11f86a3931b
  - [bpf-next,2/7] selftests/bpf: stop using relaxed_core_relocs which has no effect
    https://git.kernel.org/bpf/bpf-next/c/23a7baaa9388
  - [bpf-next,3/7] libbpf: deprecated bpf_object_open_opts.relaxed_core_relocs
    https://git.kernel.org/bpf/bpf-next/c/277641859e83
  - [bpf-next,4/7] libbpf: allow skipping attach_func_name in bpf_program__set_attach_target()
    https://git.kernel.org/bpf/bpf-next/c/2d5ec1c66e25
  - [bpf-next,5/7] selftests/bpf: switch fexit_bpf2bpf selftest to set_attach_target() API
    https://git.kernel.org/bpf/bpf-next/c/60aed22076b0
  - [bpf-next,6/7] libbpf: schedule open_opts.attach_prog_fd deprecation since v0.7
    https://git.kernel.org/bpf/bpf-next/c/91b555d73e53
  - [bpf-next,7/7] libbpf: constify all high-level program attach APIs
    https://git.kernel.org/bpf/bpf-next/c/942025c9f37e

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



      parent reply	other threads:[~2021-09-17 16:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  1:58 [PATCH bpf-next 0/7] Improve set_attach_target() and deprecate open_opts.attach_prog_fd Andrii Nakryiko
2021-09-16  1:58 ` [PATCH bpf-next 1/7] libbpf: use pre-setup sec_def in libbpf_find_attach_btf_id() Andrii Nakryiko
2021-09-16  2:52   ` Yonghong Song
2021-09-16  1:58 ` [PATCH bpf-next 2/7] selftests/bpf: stop using relaxed_core_relocs which has no effect Andrii Nakryiko
2021-09-16  2:57   ` Yonghong Song
2021-09-16  1:58 ` [PATCH bpf-next 3/7] libbpf: deprecated bpf_object_open_opts.relaxed_core_relocs Andrii Nakryiko
2021-09-16  2:57   ` Yonghong Song
2021-09-16  1:58 ` [PATCH bpf-next 4/7] libbpf: allow skipping attach_func_name in bpf_program__set_attach_target() Andrii Nakryiko
2021-09-16  4:17   ` Yonghong Song
2021-09-17 16:09     ` Alexei Starovoitov
2021-09-17 18:04       ` Andrii Nakryiko
2021-09-16  1:58 ` [PATCH bpf-next 5/7] selftests/bpf: switch fexit_bpf2bpf selftest to set_attach_target() API Andrii Nakryiko
2021-09-16  4:24   ` Yonghong Song
2021-09-16 17:14     ` Andrii Nakryiko
2021-09-16  1:58 ` [PATCH bpf-next 6/7] libbpf: schedule open_opts.attach_prog_fd deprecation since v0.7 Andrii Nakryiko
2021-09-16  4:26   ` Yonghong Song
2021-09-16  1:58 ` [PATCH bpf-next 7/7] libbpf: constify all high-level program attach APIs Andrii Nakryiko
2021-09-16  4:29   ` Yonghong Song
2021-09-17 16:10 ` 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=163189500885.20217.13882482710541336384.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).