From: Ben Hutchings <ben@decadent.org.uk>
To: Guenter Roeck <linux@roeck-us.net>, stable <stable@vger.kernel.org>
Subject: Re: Build errors in v3.16.y-stable-queue
Date: Sat, 06 Aug 2016 11:47:00 +0100 [thread overview]
Message-ID: <1470480420.4189.13.camel@decadent.org.uk> (raw)
In-Reply-To: <57A54466.6010404@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Fri, 2016-08-05 at 18:59 -0700, Guenter Roeck wrote:
>
[...]
> >
> >Current failure:
>
> Building mips:nlm_xlp_defconfig ... failed
> Building mips:cavium_octeon_defconfig ... failed
> Building mips:malta_defconfig ... failed
>
> --------------
> Error log:
> In file included from /opt/buildbot/slave/stable-queue-3.16/build/include/linux/mm.h:51:0,
> from /opt/buildbot/slave/stable-queue-3.16/build/arch/mips/kernel/asm-offsets.c:14:
> /opt/buildbot/slave/stable-queue-3.16/build/arch/mips/include/asm/pgtable.h: In function 'set_pte':
> /opt/buildbot/slave/stable-queue-3.16/build/arch/mips/include/asm/pgtable.h:192:12: error: expected ':' or ')' before 'MIPS_ISA_ARCH_LEVEL'
> " .set "MIPS_ISA_ARCH_LEVEL" \n"
> ^
> make[2]: *** [arch/mips/kernel/asm-offsets.s] Error 1
Looks like "MIPS: Adjust set_pte() SMP fix to handle R10000_LLSC_WAR"
needs all the same changes for 3.16 as it does for 3.2.
Ben.
--
Ben Hutchings
Beware of bugs in the above code;
I have only proved it correct, not tried it. - Donald Knuth
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-06 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 3:41 Build errors in v3.16.y-stable-queue Guenter Roeck
2016-07-30 20:03 ` Ben Hutchings
2016-07-31 16:08 ` Guenter Roeck
2016-08-05 23:36 ` Ben Hutchings
2016-08-06 1:59 ` Guenter Roeck
2016-08-06 10:47 ` Ben Hutchings [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=1470480420.4189.13.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.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).