There's an ordering problem around the definition of E820_X_MAX: the definition in the kernel-specific header is referred to in the user-specific header data structures, at least for x86. When compiling userspace, the user-specific header provides an alternate version of E820_X_MAX. To get around this problem, place a marker specifically to indicate the point at which the #include_next should be placed in the kernel-specific file. Signed-off-by: David Howells <dhowells@xxxxxxxxxx> --- arch/x86/include/asm/e820.h | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/arch/x86/include/asm/e820.h b/arch/x86/include/asm/e820.h index 908b969..e02512f 100644 --- a/arch/x86/include/asm/e820.h +++ b/arch/x86/include/asm/e820.h @@ -45,6 +45,8 @@ #define E820_NVS 4 #define E820_UNUSABLE 5 +// DISINTEGRATE: INCLUDE UAPI HERE + /* * reserved RAM used by kernel itself * if CONFIG_INTEL_TXT is enabled, memory of this type will be -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
