From: patchwork-bot+netdevbpf@kernel.org
To: Jianyun Gao <jianyungao89@gmail.com>
Cc: linux-kernel@vger.kernel.org, andrii@kernel.org,
eddyz87@gmail.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v4] libbpf: update the comment to remove the reference to the deprecated interface bpf_program__load().
Date: Tue, 04 Nov 2025 18:30:10 +0000 [thread overview]
Message-ID: <176228101010.2956689.5611314609382456914.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251103120727.145965-1-jianyungao89@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 3 Nov 2025 20:07:27 +0800 you wrote:
> Commit be2f2d1680df ("libbpf: Deprecate bpf_program__load() API") marked
> bpf_program__load() as deprecated starting with libbpf v0.6. And later
> in commit 146bf811f5ac ("libbpf: remove most other deprecated high-level
> APIs") actually removed the bpf_program__load() implementation and
> related old high-level APIs.
>
> This patch update the comment in bpf_program__set_attach_target() to
> remove the reference to the deprecated interface bpf_program__load().
>
> [...]
Here is the summary with links:
- [v4] libbpf: update the comment to remove the reference to the deprecated interface bpf_program__load().
https://git.kernel.org/bpf/bpf-next/c/efa47566ad0b
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:[~2025-11-04 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 12:07 [PATCH v4] libbpf: update the comment to remove the reference to the deprecated interface bpf_program__load() Jianyun Gao
2025-11-04 18:30 ` 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=176228101010.2956689.5611314609382456914.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jianyungao89@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.