From: patchwork-bot+netdevbpf@kernel.org
To: Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
martin.kelly@crowdstrike.com, slava.imameev@crowdstrike.com
Subject: Re: [PATCH bpf-next v9 0/7] libbpf: BPF program manual loading
Date: Fri, 30 Oct 2026 18:40:06 +0000 [thread overview]
Message-ID: <179338560630.1712658.8774924351807641695.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261029223348.3730738-1-andrey.grodzovsky@crowdstrike.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 29 Oct 2026 18:33:41 -0400 you wrote:
> This series was originally posted in January 2025 [1] as a two-patch RFC
> introducing a per-program tri-state load strategy (disabled/auto/manual)
> to let large BPF applications load a subset of their programs lazily,
> independent of the initial bpf_object load.
>
> Motivation:
>
> [...]
Here is the summary with links:
- [bpf-next,v9,1/7] libbpf: Reject gen_loader set after PREPARE step.
https://git.kernel.org/bpf/bpf-next/c/c9b2a0975c39
- [bpf-next,v9,2/7] libbpf: Free func_info, line_info and subprogs in bpf_program__exit()
https://git.kernel.org/bpf/bpf-next/c/899345f5d768
- [bpf-next,v9,3/7] libbpf: BPF program load strategy enum
https://git.kernel.org/bpf/bpf-next/c/5db39ae40725
- [bpf-next,v9,4/7] libbpf: BPF programs manual loading and attaching
https://git.kernel.org/bpf/bpf-next/c/354aaa519cb4
- [bpf-next,v9,5/7] libbpf: Support declarative manual load via SEC("!...") prefix
https://git.kernel.org/bpf/bpf-next/c/c29809ea29e2
- [bpf-next,v9,6/7] selftests/bpf: Cover BPF program load strategies and manual loading
https://git.kernel.org/bpf/bpf-next/c/3a59ddfaea5e
- [bpf-next,v9,7/7] selftests/bpf: Convert veristat to BPF_PROG_LOAD_STRATEGY_MANUAL
(no matching commit)
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:[~2026-10-30 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 22:33 [PATCH bpf-next v9 0/7] libbpf: BPF program manual loading Andrey Grodzovsky
2026-10-29 22:33 ` [PATCH bpf-next v9 1/7] libbpf: Reject gen_loader set after PREPARE step Andrey Grodzovsky
2026-10-29 22:33 ` [PATCH bpf-next v9 2/7] libbpf: Free func_info, line_info and subprogs in bpf_program__exit() Andrey Grodzovsky
2026-10-29 22:33 ` [PATCH bpf-next v9 3/7] libbpf: BPF program load strategy enum Andrey Grodzovsky
2026-10-29 22:33 ` [PATCH bpf-next v9 4/7] libbpf: BPF programs manual loading and attaching Andrey Grodzovsky
2026-10-29 22:54 ` sashiko-bot
2026-10-30 18:32 ` Andrii Nakryiko
2026-10-29 22:33 ` [PATCH bpf-next v9 5/7] libbpf: Support declarative manual load via SEC("!...") prefix Andrey Grodzovsky
2026-10-29 22:33 ` [PATCH bpf-next v9 6/7] selftests/bpf: Cover BPF program load strategies and manual loading Andrey Grodzovsky
2026-10-29 22:33 ` [PATCH bpf-next v9 7/7] selftests/bpf: Convert veristat to BPF_PROG_LOAD_STRATEGY_MANUAL Andrey Grodzovsky
2026-10-29 22:45 ` sashiko-bot
2026-10-30 18:32 ` Andrii Nakryiko
2026-10-30 18: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=179338560630.1712658.8774924351807641695.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=martin.kelly@crowdstrike.com \
--cc=slava.imameev@crowdstrike.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