mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mark Korenberg <socketpair@gmail.com>
Cc: qmo@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, nathan@kernel.org, morbo@google.com,
	justinstitt@google.com, emil@etsalapatis.com,
	ihor.solodrai@linux.dev, ndesaulniers@google.com,
	kuba@kernel.org, sdf@fomichev.me, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next v5 0/3] bpftool: Make the LLVM disassembler an optional runtime dependency
Date: Wed, 04 Nov 2026 00:40:06 +0000	[thread overview]
Message-ID: <179375280630.1976018.3900503813483067924.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103-bpftool-plugin-v5-0-683e08a25df0@gmail.com>

Hello:

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

On Tue, 03 Nov 2026 18:59:52 +0500 you wrote:
> libLLVM (~140 MiB on Fedora) is a hard dependency of bpftool, although it
> is only used by "bpftool prog dump jited". With this series, bpftool is
> no longer linked with libLLVM.so but loads it with dlopen() when it needs
> to disassemble JITed programs, so that distributions can make it optional.
> Patch 1 fixes a leak found on the way. Patch 2 makes "prog dump jited
> ... file FILE" work without a disassembler.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/3] bpftool: Fix disposal of the LLVM disassembler context
    https://git.kernel.org/bpf/bpf-next/c/abf197dfc622
  - [bpf-next,v5,2/3] bpftool: Don't require a disassembler to dump a JITed program to a file
    https://git.kernel.org/bpf/bpf-next/c/40dbd552e2b1
  - [bpf-next,v5,3/3] bpftool: Make the LLVM disassembler an optional runtime dependency
    https://git.kernel.org/bpf/bpf-next/c/1c9ca39c56ce

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



      parent reply	other threads:[~2026-11-04  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 13:59 Mark Korenberg via B4 Relay
2026-11-03 13:59 ` [PATCH bpf-next v5 1/3] bpftool: Fix disposal of the LLVM disassembler context Mark Korenberg via B4 Relay
2026-11-03 22:14   ` Quentin Monnet
2026-11-03 13:59 ` [PATCH bpf-next v5 2/3] bpftool: Don't require a disassembler to dump a JITed program to a file Mark Korenberg via B4 Relay
2026-11-03 22:14   ` Quentin Monnet
2026-11-03 13:59 ` [PATCH bpf-next v5 3/3] bpftool: Make the LLVM disassembler an optional runtime dependency Mark Korenberg via B4 Relay
2026-11-03 22:15   ` Quentin Monnet
2026-11-04  0: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=179375280630.1976018.3900503813483067924.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=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=socketpair@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®