This compile-test started from the strong belief that (almost) all headers should be able to be compiled as a standalone unit, but this requirement seems to be just annoying. I believe compile-test of exported headers is good. On the other hand, in-kernel headers are not necessarily supposed to be always compilable. Actually, some headers are only included under a certain combination of CONFIG options, and that is definitely fine. This test is still causing false positive errors in randconfig. Moreover, newly added headers are compile-tested by default, sometimes they catch (not fatal) bugs, but often raise false positive errors to end up with making people upset. The merge window is closing shortly, so there is not much I can do. Disable it for now, and take a pause to re-think whether we should continue this or change the course. Signed-off-by: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx> --- init/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/init/Kconfig b/init/Kconfig index 9697c6b5303c..778551a1a13c 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -111,6 +111,7 @@ config HEADER_TEST config KERNEL_HEADER_TEST bool "Compile test kernel headers" depends on HEADER_TEST + depends on BROKEN # disabled for now help Headers in include/ are used to build external moduls. Compile test them to ensure they are self-contained, i.e. -- 2.17.1
