From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Markos Chandras <markos.chandras@imgtec.com>
Subject: Re: linux-next: Tree for Feb 17 (mips build failures)
Date: Tue, 17 Feb 2015 09:20:36 -0800 [thread overview]
Message-ID: <20150217172036.GA29820@roeck-us.net> (raw)
In-Reply-To: <20150217160221.1a15340e@canb.auug.org.au>
On Tue, Feb 17, 2015 at 04:02:21PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150216:
>
> The slave-dma tree lost its build failure.
>
> Non-merge commits (relative to Linus' tree): 2980
> 2871 files changed, 124415 insertions(+), 70264 deletions(-)
>
> ----------------------------------------------------------------------------
>
[ maybe I got it right this time ]
Build results:
total: 121 pass: 109 fail: 12
Failed builds:
mips:defconfig
mips:allmodconfig
mips:bcm47xx_defconfig
mips:bcm63xx_defconfig
mips:nlm_xlp_defconfig
mips:ath79_defconfig
mips:ar7_defconfig
mips:fuloong2e_defconfig
mips:e55_defconfig
mips:cavium_octeon_defconfig
mips:malta_defconfig
sparc64:allmodconfig
mips builds are all failing with
Building mips:defconfig ... failed
--------------
Error log:
arch/mips/kernel/genex.S: Assembler messages:
arch/mips/kernel/genex.S:128: Error: Bad value (mips64r6) for internal use
arch/mips/kernel/genex.S:128: Error: unknown ISA level 64r6
This was introduced by commit 0bf705e94771800 ("MIPS: kernel: genex: Set
correct ISA level") which apparently assumes that only mips64r6 is a valid
ISA level, though it is obviously not supported on older compilers. This
is on top of the other mips r6 related build errors seen yesterday.
I really hope that this is not 3.20 material, given the lack of testing
with architectures other than mips r6 or with older compilers.
Guenter
next prev parent reply other threads:[~2015-02-17 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 5:02 linux-next: Tree for Feb 17 Stephen Rothwell
2015-02-17 17:20 ` Guenter Roeck [this message]
2015-02-17 20:37 ` linux-next: Tree for Feb 17 (mips build failures) Stephen Rothwell
2015-02-18 9:14 ` Markos Chandras
2015-02-18 13:54 ` Guenter Roeck
2015-02-18 14:02 ` Markos Chandras
2015-02-17 18:28 ` linux-next: Tree for Feb 17 (i2c-designware-baytrail.c) Randy Dunlap
2015-02-17 19:11 ` Wolfram Sang
2015-02-17 20:59 ` David E. Box
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=20150217172036.GA29820@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=markos.chandras@imgtec.com \
--cc=sfr@canb.auug.org.au \
/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