[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <mhng-c280d48c-477d-4589-baee-255c774b5a51@palmer-mbp2014>
Date: Fri, 01 Apr 2022 10:55:00 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: mkl@...gutronix.de, aurelien@...el32.net,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Kito Cheng <kito.cheng@...il.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, linux-riscv@...ts.infradead.org,
linux-sparse@...r.kernel.org, ukl@...gutronix.de,
luc.vanoostenryck@...il.com
Subject: Re: [PATCH] riscv: fix build with binutils 2.38
On Fri, 01 Apr 2022 10:14:03 PDT (-0700), Linus Torvalds wrote:
> On Thu, Mar 31, 2022 at 11:53 PM Marc Kleine-Budde <mkl@...gutronix.de> wrote:
>>
>> | WARNING: invalid argument to '-march': 'zicsr_zifencei'
>
> Gaah, it works but still warns because I cut-and-pasted those
> zicsr/zifencei options from some random source that had them
> capitalized and I didn't look closely enough at the reports.
>
> Anyway, hopefully somebody can bother to fix up that. Possibly by
> changing the strncmp to a strnicmp - but I don't know what the rules
> for lower-case vs capitals are for the other options. I'm still busy
> with the kernel merge window, so this gets archived on my side..
I'm gluing sparse to my build tests now, so I'll sort it out (that'll
also make sure a failure doesn't leak again). Might not be today, but
shouldn't take too long.
Powered by blists - more mailing lists