[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5484BF4D.1020809@de.ibm.com>
Date: Sun, 07 Dec 2014 21:57:49 +0100
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the access_once tree
Am 05.12.2014 um 11:32 schrieb Stephen Rothwell:
> Hi Christian,
>
> After merging the access_once tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/linux/compiler.h:189:0,
> from include/uapi/linux/stddef.h:1,
> from include/linux/stddef.h:4,
> from include/uapi/linux/posix_types.h:4,
> from include/linux/fdtable.h:8,
> from security/apparmor/domain.c:16:
> include/linux/types.h:14:9: error: unknown type name '__kernel_fd_set'
> typedef __kernel_fd_set fd_set;
> ^
>
> And many more :-(
>
> Presumably caused by commit b06f66134856 ("kernel: Provide READ_ONCE
> and ASSIGN_ONCE") which added types.h into compiler.h, but I am not
> sure. It could be an interaction with something else in linux-next, of
> course.
>
> I have dropped the access_once tree for today, sorry.
>
Interesting, I double checked with defconfig and cross compilation. But yes, using allmodconfig fails.
I have changed that to uapi/linux/types.h and __u<xx>. This seems to fix it as it only adds a small set of types.
Can you re-add?
Christian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists