Linus Torvalds writes: (Summary) And doing a trivial "git bisect run" to pinpoint where
CONFIG_64BIT goes away gives us
CONFIG_64BIT goes away gives us
f467c5640c29ad258c3cd8186a776c82fc3b8057 is the first bad commit f467c5640c29ad258c3cd8186a776c82fc3b8057 is the first bad commit which does that
which does that
"kconfig: only write '# CONFIG_FOO is not set' for visible symbols" "kconfig: only write '# CONFIG_FOO is not set' for visible symbols" and it turns out that CONFIG_64BIT is not a visible symbol on x86-32, because that question is disabled when ARCH != "x86".
CONFIG_64BIT goes away gives us
f467c5640c29ad258c3cd8186a776c82fc3b8057 is the first bad commit f467c5640c29ad258c3cd8186a776c82fc3b8057 is the first bad commit which does that
which does that
"kconfig: only write '# CONFIG_FOO is not set' for visible symbols" "kconfig: only write '# CONFIG_FOO is not set' for visible symbols" and it turns out that CONFIG_64BIT is not a visible symbol on x86-32, because that question is disabled when ARCH != "x86".