There's an ordering problem around the definition of u_quad_t in linux/coda.h:
the definition in the kernel-specific header is referred to in the
user-specific header data structures. When compiling userspace, the
user-specific header provides an alternate version of u_quad_t.
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>
---
include/linux/coda.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/coda.h b/include/linux/coda.h
index 96c8769..5a2c1a0 100644
--- a/include/linux/coda.h
+++ b/include/linux/coda.h
@@ -111,6 +111,7 @@ typedef unsigned long long u_quad_t;
#else
#define cdev_t dev_t
#endif
+// DISINTEGRATE: INCLUDE UAPI HERE
#ifdef __CYGWIN32__
struct timespec {
--
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
