From: James Hogan <james.hogan@imgtec•com>
To: Mark Brown <broonie@kernel•org>
Cc: Kees Cook <keescook@chromium•org>,
Andrew Morton <akpm@linux-foundation•org>,
kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: next-20150806 build: 2 failures 52 warnings (next-20150806)
Date: Thu, 6 Aug 2015 22:52:05 +0100 [thread overview]
Message-ID: <20150806215205.GB14493@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <20150806172752.GA20873@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
Hi Mark,
On Thu, Aug 06, 2015 at 06:27:52PM +0100, Mark Brown wrote:
> On Thu, Aug 06, 2015 at 12:00:47PM +0100, Build bot for Mark Brown wrote:
>
> Today's linux-next fails to build an ARM allmodconfig with:
>
> > arm-allmodconfig
> > ../lib/test_user_copy.c:67:2: error: implicit declaration of function 'copy_in_user' [-Werror=implicit-function-declaration]
> > ../lib/test_user_copy.c:94:2: error: implicit declaration of function '__copy_in_user' [-Werror=implicit-function-declaration]
>
> due to 3a646f02c7 (lib/test_user_copy.c: check
> __copy_in_user()/copy_in_user()) which attempts to test copy_in_user()
> which doesn't appear to be defined, at least with the set of include
> files and/or config options you get with an allmodconfig and not at all
> as far as I can tell.
Yeh, the copy_in_user ones need to be conditional upon CONFIG_COMPAT.
Sorry for the breakage. I've asked Andrew to drop them until I can get a
v2 patchset out tomorrow.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-06 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:00 next-20150806 build: 2 failures 52 warnings (next-20150806) Build bot for Mark Brown
2015-08-06 17:19 ` Mark Brown
2015-08-06 18:50 ` Andy Gross
2015-08-06 17:27 ` Mark Brown
2015-08-06 21:52 ` James Hogan [this message]
2015-08-06 17:53 ` Mark Brown
2015-08-06 21:39 ` Stephen Rothwell
2015-08-07 1:56 ` Jiang Liu
2015-08-07 9:49 ` Mark Brown
2015-08-10 18:31 ` Bjorn Helgaas
2015-08-12 8:21 ` Jiang Liu
2015-08-18 12:47 ` Thomas Gleixner
2015-08-06 18:01 ` Mark Brown
2015-08-06 20:17 ` Joerg Roedel
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=20150806215205.GB14493@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=keescook@chromium$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.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