From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org, bjorn@rivosinc.com,
jean-philippe@linaro.org, zachary.leaf@arm.com,
quentin@isovalent.com
Subject: Re: [PATCH bpf-next v2] selftests/bpf: Cross-compile bpftool
Date: Wed, 15 Feb 2023 17:00:17 +0000 [thread overview]
Message-ID: <167648041794.12108.7209836979212211534.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230214161253.183458-1-bjorn@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 14 Feb 2023 17:12:53 +0100 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> When the BPF selftests are cross-compiled, only the a host version of
> bpftool is built. This version of bpftool is used on the host-side to
> generate various intermediates, e.g., skeletons.
>
> The test runners are also using bpftool, so the Makefile will symlink
> bpftool from the selftest/bpf root, where the test runners will look
> the tool:
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: Cross-compile bpftool
https://git.kernel.org/bpf/bpf-next/c/5e53e5c7edc6
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:[~2023-02-15 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:12 [PATCH bpf-next v2] selftests/bpf: Cross-compile bpftool Björn Töpel
2023-02-15 17:00 ` 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=167648041794.12108.7209836979212211534.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jean-philippe@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=zachary.leaf@arm.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;
as well as URLs for NNTP newsgroup(s).