[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221020103823.31001-1-ashimida@linux.alibaba.com>
Date: Thu, 20 Oct 2022 03:38:23 -0700
From: Dan Li <ashimida@...ux.alibaba.com>
To: masahiroy@...nel.org, michal.lkml@...kovi.net,
ndesaulniers@...gle.com, corbet@....net
Cc: linux-kbuild@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Dan Li <ashimida@...ux.alibaba.com>
Subject: [RFC] Documentation: kbuild: Add description of git for reproducible builds
The status of git will affect the final compilation result, add it to
the documentation of reproducible builds.
Signed-off-by: Dan Li <ashimida@...ux.alibaba.com>
---
Documentation/kbuild/reproducible-builds.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/kbuild/reproducible-builds.rst b/Documentation/kbuild/reproducible-builds.rst
index 071f0151a7a4..13397f38c358 100644
--- a/Documentation/kbuild/reproducible-builds.rst
+++ b/Documentation/kbuild/reproducible-builds.rst
@@ -119,6 +119,16 @@ To avoid this, you can make the vDSO different for different
kernel versions by including an arbitrary string of "salt" in it.
This is specified by the Kconfig symbol ``CONFIG_BUILD_SALT``.
+Git
+-----------------------
+
+Uncommitted changes or different commit ids in git can also lead
+to different compilation results. For example, after executing
+``git reset HEAD^``, even if the code is the same, the
+``include/config/kernel.release`` generated during compilation
+will be different, which will eventually lead to binary differences.
+See ``scripts/setlocalversion`` for details.
+
.. _KBUILD_BUILD_TIMESTAMP: kbuild.html#kbuild-build-timestamp
.. _KBUILD_BUILD_USER and KBUILD_BUILD_HOST: kbuild.html#kbuild-build-user-kbuild-build-host
.. _KCFLAGS: kbuild.html#kcflags
--
2.17.1
Powered by blists - more mailing lists