From: sashiko-bot@kernel.org
To: "Sasha Levin" <sashal@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH 2/6] kbuild: add "make tools_build" to build userspace tools from tools/
Date: Sun, 11 Oct 2026 23:45:58 +0000 [thread overview]
Message-ID: <sashiko-outbox-167521@kernel.org> (raw)
In-Reply-To: <20261011233647.2454648-3-sashal@kernel.org>
> The programs under tools/ have their own build systems and are not built
> by "make", so nothing builds them together with the kernel they belong
> to, and breakage in them is only noticed when someone happens to build
> them by hand, sometimes many stable releases later.
>
> Add a "Build userspace tools from tools/" menu (CONFIG_TOOLS_BUILD) with
> an entry for each tool, and a "tools_build" target that builds the
> selected ones for the target:
>
> - Each tool is built by its own build system, as it is built
> standalone, into tools-build/ in the object tree. "make clean" removes
> that directory without running the tools' own clean rules.
>
> - The compiler is the one CONFIG_CC_CAN_LINK was tested with: $(CC),
> USERCFLAGS and KBUILD_USERABI, so cross builds, including LLVM=1
> [ ... ]
> The first entries are the tools that only need a C library: bootconfig,
> counter, dma, gpio, hv, iio, spi and usb.
>
> Assisted-by: LLM
> Signed-off-by: Sasha Levin <sashal@kernel.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261011233647.2454648-1-sashal@kernel.org?part=2
next prev parent reply other threads:[~2026-10-11 23:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 23:36 [RFC PATCH 0/6] kbuild: build the userspace tools in tools/ with the kernel Sasha Levin
2026-10-11 23:36 ` [RFC PATCH 1/6] kbuild: factor the userspace ABI flags out into KBUILD_USERABI Sasha Levin
2026-10-11 23:39 ` sashiko-bot
2026-10-11 23:36 ` [RFC PATCH 2/6] kbuild: add "make tools_build" to build userspace tools from tools/ Sasha Levin
2026-10-11 23:45 ` sashiko-bot [this message]
2026-10-11 23:36 ` [RFC PATCH 3/6] tools: build perf in tools_build Sasha Levin
2026-10-11 23:43 ` sashiko-bot
2026-10-12 22:07 ` Ian Rogers
2026-10-11 23:36 ` [RFC PATCH 4/6] tools: build kernel selftests " Sasha Levin
2026-10-11 23:46 ` sashiko-bot
2026-10-11 23:36 ` [RFC PATCH 5/6] kbuild: build the tools selected in tools/Kconfig as part of "make all" Sasha Levin
2026-10-11 23:44 ` sashiko-bot
2026-10-11 23:36 ` [RFC PATCH 6/6] Documentation: describe building tools with the kernel Sasha Levin
2026-10-11 23:39 ` sashiko-bot
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=sashiko-outbox-167521@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sashiko-reviews@lists.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