From: patchwork-bot+netdevbpf@kernel.org
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, nathan@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next] scripts/gen-btf.sh: Fix .btf.o generation when compiling for RISCV
Date: Tue, 30 Dec 2025 18:40:06 +0000 [thread overview]
Message-ID: <176712000605.3329931.5334657371123861484.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251229202823.569619-1-ihor.solodrai@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 29 Dec 2025 12:28:23 -0800 you wrote:
> gen-btf.sh emits a .btf.o file with BTF sections to be linked into
> vmlinux in link-vmlinux.sh
>
> This .btf.o file is created by compiling an emptystring with ${CC},
> and then adding BTF sections into it with ${OBJCOPY}.
>
> To ensure the .btf.o is linkable when cross-compiling with LLVM, we
> have to also pass ${KBUILD_FLAGS}, which in particular control the
> target word size.
>
> [...]
Here is the summary with links:
- [bpf-next] scripts/gen-btf.sh: Fix .btf.o generation when compiling for RISCV
https://git.kernel.org/bpf/bpf-next/c/600605853f87
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-12-30 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 20:28 [PATCH bpf-next] scripts/gen-btf.sh: Fix .btf.o generation when compiling for RISCV Ihor Solodrai
2025-12-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=176712000605.3329931.5334657371123861484.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=ihor.solodrai@linux.dev \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=nathan@kernel.org \
/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