From: patchwork-bot+netdevbpf@kernel.org
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: shuah@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
quentin@isovalent.com, linux-kselftest@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next] selftests/bpf: Build testing_helpers.o out of tree
Date: Thu, 02 Dec 2021 20:00:09 +0000 [thread overview]
Message-ID: <163847520932.12330.16820896026323277205.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211201145101.823159-1-jean-philippe@linaro.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 1 Dec 2021 14:51:02 +0000 you wrote:
> Add $(OUTPUT) prefix to testing_helpers.o, so it can be built out of
> tree when necessary. At the moment, in addition to being built in-tree
> even when out-of-tree is required, testing_helpers.o is not built with
> the right recipe when cross-building.
>
> For consistency the other helpers, cgroup_helpers and trace_helpers, can
> also be passed as objects instead of source. Use *_HELPERS variable to
> keep the Makefile readable.
>
> [...]
Here is the summary with links:
- [v2,bpf-next] selftests/bpf: Build testing_helpers.o out of tree
https://git.kernel.org/bpf/bpf-next/c/eee9a6df0eed
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:[~2021-12-02 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 14:51 [PATCH v2 bpf-next] selftests/bpf: Build testing_helpers.o out of tree Jean-Philippe Brucker
2021-12-02 20: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=163847520932.12330.16820896026323277205.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=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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