From: Jens Axboe <axboe@kernel.dk>
To: Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: kernel-hwcap.h change causing full kernel rebuilds
Date: Tue, 21 Apr 2026 06:52:55 -0600 [thread overview]
Message-ID: <52fb2e8f-3e1c-4cf5-a02a-0d68beedd18b@kernel.dk> (raw)
Hi,
Maybe this has already been reported, but a quick search on lore did
not find anything. So here goes... After commit:
commit abed23c3c44f565dc812563ac015be70dd61e97b
Author: Mark Brown <broonie@kernel.org>
Date: Mon Mar 2 22:53:16 2026 +0000
arm64/hwcap: Generate the KERNEL_HWCAP_ definitions for the hwcaps
arch/arm64/include/generated/asm/kernel-hwcap.h is generated for
_every build_, which means that you can literally run make back to back
without _any_ source changes and you are rewarded with a full kernel
rebuild. Not sure how this ever got past any kind of testing, because
it's very noticeable.
For now I've reverted this change locally as any kind of testing now
kicks off a full build, when a single file rebuild is all that is
needed.
--
Jens Axboe
next reply other threads:[~2026-04-21 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 12:52 Jens Axboe [this message]
2026-04-21 12:56 ` kernel-hwcap.h change causing full kernel rebuilds Joey Gouly
2026-04-21 13:00 ` Jens Axboe
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=52fb2e8f-3e1c-4cf5-a02a-0d68beedd18b@kernel.dk \
--to=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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