From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: 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>
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150716/22949c09/attachment-0001.sig>
parent reply other threads:[~2015-07-16 13:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1ZFg2R-0001bO-R5@optimist>]
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.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).