From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, bpf@vger.kernel.org,
linux-perf-users@vger.kernel.org, alexghiti@rivosinc.com,
acme@redhat.com, jean-philippe@linaro.org, qmo@kernel.org,
andrii.nakryiko@gmail.com, bjorn@rivosinc.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org,
davidlt@rivosinc.com, namhyung@kernel.org
Subject: Re: [PATCH bpf v2] tools: Override makefile ARCH variable if defined, but empty
Date: Wed, 11 Dec 2024 22:32:33 +0000 [thread overview]
Message-ID: <173395635324.1729195.17131106959498810013.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241127101748.165693-1-bjorn@kernel.org>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 27 Nov 2024 11:17:46 +0100 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> There are a number of tools (bpftool, selftests), that require a
> "bootstrap" build. Here, a bootstrap build is a build host variant of
> a target. E.g., assume that you're performing a bpftool cross-build on
> x86 to riscv, a bootstrap build would then be an x86 variant of
> bpftool. The typical way to perform the host build variant, is to pass
> "ARCH=" in a sub-make. However, if a variable has been set with a
> command argument, then ordinary assignments in the makefile are
> ignored.
>
> [...]
Here is the summary with links:
- [bpf,v2] tools: Override makefile ARCH variable if defined, but empty
https://git.kernel.org/riscv/c/537a2525eaf7
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:[~2024-12-11 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 10:17 [PATCH bpf v2] tools: Override makefile ARCH variable if defined, but empty Björn Töpel
2024-11-27 11:53 ` Jiri Olsa
2024-11-28 13:07 ` Toke Høiland-Jørgensen
2024-11-29 16:20 ` patchwork-bot+netdevbpf
2024-12-11 22:32 ` patchwork-bot+linux-riscv [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=173395635324.1729195.17131106959498810013.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=acme@redhat.com \
--cc=alexghiti@rivosinc.com \
--cc=andrii.nakryiko@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=bpf@vger.kernel.org \
--cc=davidlt@rivosinc.com \
--cc=jean-philippe@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=qmo@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