public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
	yatsenko@meta.com
Subject: Re: [PATCH bpf-next v2] libbpf: Fix BTF handling in bpf_program__clone()
Date: Thu, 02 Apr 2026 20:10:05 +0000	[thread overview]
Message-ID: <177516060505.600333.17051578920801291723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260401151640.356419-1-mykyta.yatsenko5@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed,  1 Apr 2026 16:16:40 +0100 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
> 
> Align bpf_program__clone() with bpf_object_load_prog() by gating
> BTF func/line info on FEAT_BTF_FUNC kernel support, and resolve
> caller-provided prog_btf_fd before checking obj->btf so that callers
> with their own BTF can use clone() even when the object has no BTF
> loaded.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] libbpf: Fix BTF handling in bpf_program__clone()
    https://git.kernel.org/bpf/bpf-next/c/1cc96e0e2048

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



      reply	other threads:[~2026-04-02 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 15:16 [PATCH bpf-next v2] libbpf: Fix BTF handling in bpf_program__clone() Mykyta Yatsenko
2026-04-02 20: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=177516060505.600333.17051578920801291723.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=kafai@meta.com \
    --cc=kernel-team@meta.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=yatsenko@meta.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