diff options
author | 2021-06-12 15:18:38 +0100 | |
---|---|---|
committer | 2021-06-17 10:01:12 +0900 | |
commit | a979522a1a88556e42a22ce61bccc58e304cb361 (patch) | |
tree | b614804f871ab8b5cbbd5e1eed311bcc347f2b77 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | kbuild: modpost: Explicitly warn about unprototyped symbols (diff) | |
download | wireguard-linux-a979522a1a88556e42a22ce61bccc58e304cb361.tar.xz wireguard-linux-a979522a1a88556e42a22ce61bccc58e304cb361.zip |
kbuild: mkcompile_h: consider timestamp if KBUILD_BUILD_TIMESTAMP is set
To avoid unnecessary recompilations, mkcompile_h does not regenerate
compile.h if just the timestamp changed.
Though, if KBUILD_BUILD_TIMESTAMP is set, an explicit timestamp for the
build was requested, in which case we should not ignore it.
If a user follows the documentation for reproducible builds [1] and
defines KBUILD_BUILD_TIMESTAMP as the git commit timestamp, a clean
build will have the correct timestamp. A subsequent cherry-pick (or
amend) changes the commit timestamp and if an incremental build is done
with a different KBUILD_BUILD_TIMESTAMP now, that new value is not taken
into consideration. But it should for reproducibility.
Hence, whenever KBUILD_BUILD_TIMESTAMP is explicitly set, do not ignore
UTS_VERSION when making a decision about whether the regenerated version
of compile.h should be moved into place.
[1] https://www.kernel.org/doc/html/latest/kbuild/reproducible-builds.html
Signed-off-by: Matthias Maennich <maennich@google.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions