From: Conor Dooley <conor@kernel.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Chanho Park <chanho61.park@samsung.com>,
Bin Meng <bmeng.cn@gmail.com>,
palmer@dabbelt.com, u-boot@lists.denx.de
Subject: Re: [PATCH v1] riscv: cpu: improve multi-letter extension detection in supports_extension()
Date: Tue, 5 Mar 2024 18:38:49 +0000 [thread overview]
Message-ID: <20240305-squire-musty-bbd192df3780@spud> (raw)
In-Reply-To: <41a27290-5b44-4e8a-8718-8bbe945fd456@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
On Tue, Mar 05, 2024 at 09:10:59AM +0100, Heinrich Schuchardt wrote:
> On 3/5/24 08:54, Conor Dooley wrote:
> > On Tue, Mar 05, 2024 at 08:34:20AM +0100, Heinrich Schuchardt wrote:
> > > On 3/5/24 00:28, Conor Dooley wrote:
> > > > From: Conor Dooley <conor.dooley@microchip.com>
> > > According to
> > > https://github.com/riscv/riscv-isa-manual/blob/main/src/naming.adoc the
> > > ISA string is case insensitive. Why can we assume here that it is lower
> > > case?
> >
> > The binding does not allow upper-case.
>
> Ok. That is in Linux'
> Documentation/devicetree/bindings/riscv/extensions.yaml.
Right. I should've linked to that, sorry.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-03-05 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 23:28 [PATCH v1] riscv: cpu: improve multi-letter extension detection in supports_extension() Conor Dooley
2024-03-05 7:34 ` Heinrich Schuchardt
2024-03-05 7:54 ` Conor Dooley
2024-03-05 8:10 ` Heinrich Schuchardt
2024-03-05 18:38 ` Conor Dooley [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=20240305-squire-musty-bbd192df3780@spud \
--to=conor@kernel.org \
--cc=bmeng.cn@gmail.com \
--cc=chanho61.park@samsung.com \
--cc=conor.dooley@microchip.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=palmer@dabbelt.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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