From: Palmer Dabbelt <palmer@dabbelt.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mkl@pengutronix.de, aurelien@aurel32.net,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Kito Cheng <kito.cheng@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-sparse@vger.kernel.org, ukl@pengutronix.de,
luc.vanoostenryck@gmail.com
Subject: Re: [PATCH] riscv: fix build with binutils 2.38
Date: Fri, 01 Apr 2022 10:55:00 -0700 (PDT) [thread overview]
Message-ID: <mhng-c280d48c-477d-4589-baee-255c774b5a51@palmer-mbp2014> (raw)
In-Reply-To: <CAHk-=wgv6rXFjTdaumFgDC4ixg6QMOL83sQ2XOqvJC0h5fLX2g@mail.gmail.com>
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@pengutronix.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.
prev parent reply other threads:[~2022-04-01 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220126171442.1338740-1-aurelien@aurel32.net>
[not found] ` <20220331103247.y33wvkxk5vfbqohf@pengutronix.de>
[not found] ` <20220331103913.2vlneq6clnheuty6@pengutronix.de>
2022-03-31 10:51 ` [PATCH] riscv: fix build with binutils 2.38 Marc Kleine-Budde
2022-03-31 17:05 ` Aurelien Jarno
2022-03-31 18:16 ` Linus Torvalds
2022-03-31 19:42 ` Palmer Dabbelt
2022-04-01 6:53 ` Marc Kleine-Budde
2022-04-01 17:14 ` Linus Torvalds
2022-04-01 17:55 ` Palmer Dabbelt [this message]
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=mhng-c280d48c-477d-4589-baee-255c774b5a51@palmer-mbp2014 \
--to=palmer@dabbelt.com \
--cc=aou@eecs.berkeley.edu \
--cc=aurelien@aurel32.net \
--cc=kito.cheng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mkl@pengutronix.de \
--cc=paul.walmsley@sifive.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ukl@pengutronix.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).