From: Mark Brown <broonie@kernel•org>
To: Eric B Munson <emunson@akamai•com>,
Andrew Morton <akpm@linux-foundation•org>
Cc: 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-20150716 build: 4 failures 88 warnings (next-20150716)
Date: Thu, 16 Jul 2015 14:59:41 +0100 [thread overview]
Message-ID: <20150716135941.GK4039@sirena.org.uk> (raw)
In-Reply-To: <E1ZFg2R-0001bO-R5@optimist>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Thu, Jul 16, 2015 at 11:05:11AM +0100, Build bot for Mark Brown wrote:
Today's -next fails to build an arm64 defconfig and allmodconfig due to
"mm: mlock: add new mlock, munlock, and munlockall system calls" which
triggers:
> ../arch/arm64/include/asm/unistd32.h:801:1: error: array index in initializer exceeds array bounds
> ../arch/arm64/include/asm/unistd32.h:801:1: error: (near initialization for 'compat_sys_call_table')
> ../arch/arm64/include/asm/unistd32.h:803:1: error: array index in initializer exceeds array bounds
> ../arch/arm64/include/asm/unistd32.h:803:1: error: (near initialization for 'compat_sys_call_table')
> ../arch/arm64/include/asm/unistd32.h:805:1: error: array index in initializer exceeds array bounds
> ../arch/arm64/include/asm/unistd32.h:805:1: error: (near initialization for 'compat_sys_call_table')
since it adds new syscalls but does not update __NR_compat_syscalls in
arch/arm64/include/asm/unistd.h so there are no array slots for the new
data.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-07-16 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 10:05 next-20150716 build: 4 failures 88 warnings (next-20150716) Build bot for Mark Brown
2015-07-16 13:41 ` Mark Brown
2015-07-16 13:48 ` Catalin Marinas
2015-07-16 14:01 ` Mark Brown
2015-07-16 21:29 ` Andrew Morton
2015-07-16 13:59 ` Mark Brown [this message]
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=20150716135941.GK4039@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=emunson@akamai$(echo .)com \
--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