On Wed, Feb 18, 2015 at 05:54:57AM -0800, Guenter Roeck wrote:
> 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@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxx
> >
> > 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
>
Hi,
Yes, all the recent build failures because of the r6 patches are now fixed.
--
markos
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
