From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christian Borntraeger <borntraeger@de•ibm.com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build failure after merge of the access_once tree
Date: Fri, 5 Dec 2014 21:32:24 +1100 [thread overview]
Message-ID: <20141205213224.2dcc20e9@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-12-05 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 10:32 Stephen Rothwell [this message]
2014-12-07 20:57 ` linux-next: build failure after merge of the access_once tree Christian Borntraeger
2014-12-07 21:16 ` Christian Borntraeger
2014-12-07 23:55 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2014-12-08 11:26 Stephen Rothwell
2014-12-08 11:35 ` Christian Borntraeger
2014-12-09 19:54 ` Christian Borntraeger
2014-12-10 8:20 Stephen Rothwell
2014-12-10 11:20 ` Christian Borntraeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141205213224.2dcc20e9@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox