[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8a6be2c-2dcb-fe58-2c32-e3baa357819c@wdc.com>
Date: Fri, 26 Jul 2019 15:20:47 -0700
From: Atish Patra <atish.patra@....com>
To: Paul Walmsley <paul.walmsley@...ive.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alan Kao <alankao@...estech.com>,
Albert Ou <aou@...s.berkeley.edu>,
Allison Randal <allison@...utok.net>,
Anup Patel <Anup.Patel@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Johan Hovold <johan@...nel.org>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
Palmer Dabbelt <palmer@...ive.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 3/4] RISC-V: Support case insensitive ISA string parsing.
On 7/26/19 1:47 PM, Paul Walmsley wrote:
> On Fri, 26 Jul 2019, Atish Patra wrote:
>
>> As per riscv specification, ISA naming strings are
>> case insensitive. However, currently only lower case
>> strings are parsed during cpu procfs.
>>
>> Support parsing of upper case letters as well.
>>
>> Signed-off-by: Atish Patra <atish.patra@....com>
>
> Is there a use case that's driving this, or
Currently, we use all lower case isa string in kvmtool. But somebody can
have uppercase letters in future as spec allows it.
can we just say, "use
> lowercase letters" and leave it at that?
>
In that case, it will not comply with RISC-V spec. Is that okay ?
>
> - Paul
>
--
Regards,
Atish
Powered by blists - more mailing lists