All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Markos Chandras <markos.chandras@imgtec.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: linux-next: Tree for Feb 17 (mips build failures)
Date: Wed, 18 Feb 2015 05:54:57 -0800	[thread overview]
Message-ID: <54E499B1.7060303@roeck-us.net> (raw)
In-Reply-To: <20150218091436.GA14404@mchandras-linux.le.imgtec.org>

On 02/18/2015 01:14 AM, Markos Chandras wrote:
> On Wed, Feb 18, 2015 at 07:37:40AM +1100, Stephen Rothwell wrote:
>> Hi Guenter,
>>
>> [Add Ralf to cc]
>>
>> On Tue, 17 Feb 2015 09:20:36 -0800 Guenter Roeck <linux@roeck-us.net> wrote:
>>>
>>> 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.
>>
>> --
>> Cheers,
>> Stephen Rothwell                    sfr@canb.auug.org.au
>
> This is just a typo I introduced yesterday by mistake. This has been fixed in
> the meantime but it did not make it in today's linux-next.
>
Yes, but it is not the only r6 related bug. Did you fix all the others as well ?

Guenter

  reply	other threads:[~2015-02-18 13:54 UTC|newest]

Thread overview: 11+ 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 ` linux-next: Tree for Feb 17 (mips build failures) Guenter Roeck
2015-02-17 20:37   ` Stephen Rothwell
2015-02-18  9:14     ` Markos Chandras
2015-02-18  9:14       ` Markos Chandras
2015-02-18 13:54       ` Guenter Roeck [this message]
2015-02-18 14:02         ` Markos Chandras
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=54E499B1.7060303@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=ralf@linux-mips.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.