Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752499AbbBRN4m (ORCPT ); Wed, 18 Feb 2015 08:56:42 -0500 Received: from bh-25.webhostbox.net ([208.91.199.152]:35846 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752340AbbBRN4k (ORCPT ); Wed, 18 Feb 2015 08:56:40 -0500 Message-ID: <54E499B1.7060303@roeck-us.net> Date: Wed, 18 Feb 2015 05:54:57 -0800 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Markos Chandras , Stephen Rothwell CC: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Ralf Baechle Subject: Re: linux-next: Tree for Feb 17 (mips build failures) References: <20150217160221.1a15340e@canb.auug.org.au> <20150217172036.GA29820@roeck-us.net> <20150218073740.71da0354@canb.auug.org.au> <20150218091436.GA14404@mchandras-linux.le.imgtec.org> In-Reply-To: <20150218091436.GA14404@mchandras-linux.le.imgtec.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-CTCH-PVer: 0000001 X-CTCH-Spam: Unknown X-CTCH-VOD: Unknown X-CTCH-Flags: 0 X-CTCH-RefID: str=0001.0A020204.54E499FE.019F,ss=1,re=0.001,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-Score: 0.001 X-CTCH-ScoreCust: 0.000 X-CTCH-Rules: C_4847, X-CTCH-SenderID: linux@roeck-us.net X-CTCH-SenderID-Flags: 0 X-CTCH-SenderID-TotalMessages: 2 X-CTCH-SenderID-TotalSpam: 0 X-CTCH-SenderID-TotalSuspected: 0 X-CTCH-SenderID-TotalConfirmed: 0 X-CTCH-SenderID-TotalBulk: 0 X-CTCH-SenderID-TotalVirus: 0 X-CTCH-SenderID-TotalRecipients: 0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: mailgid no entry from get_relayhosts_entry X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1958 Lines: 57 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 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/