From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
Alistair Francis <Alistair.Francis@wdc.com>,
ajones@ventanamicro.com, apatel@ventanamicro.com,
atishp@atishpatra.org, jrtc27@jrtc27.com, rick@andestech.com,
ycliang@andestech.com, oleksii.kurochko@gmail.com,
linux-riscv@lists.infradead.org, qemu-riscv@nongnu.org,
u-boot@lists.denx.de, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: riscv: deprecate riscv,isa
Date: Thu, 22 Jun 2023 19:59:32 +0100 [thread overview]
Message-ID: <20230622-stipend-flashily-97917469f39b@spud> (raw)
In-Reply-To: <mhng-aa00c037-6201-4548-9036-1d6dbbfc9343@palmer-ri-x1c9a>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
On Thu, Jun 22, 2023 at 11:25:35AM -0700, Palmer Dabbelt wrote:
> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> I'm not wed to any particular encoding for the properties, IMO that's more
> of a decision for the DT folks. IMO the important bit is to just get away
> from ISA strings and move towards some tightly-specified properties that
> indicate how the HW actually behaves.
I'm going to resubmit with Rob's list of strings. I'll keep your tags,
since the spirit of the patch will be the same, with enforced meanings
for each extension.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-22 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:54 [PATCH v2] dt-bindings: riscv: deprecate riscv,isa Conor Dooley
2023-06-08 17:49 ` Rob Herring
2023-06-08 18:05 ` Conor Dooley
2023-06-09 14:03 ` Rob Herring
2023-06-09 14:20 ` Conor Dooley
2023-06-22 18:25 ` Palmer Dabbelt
2023-06-22 18:59 ` Conor Dooley [this message]
2023-06-22 19:43 ` Palmer Dabbelt
2023-07-03 15:02 ` Ben Dooks
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=20230622-stipend-flashily-97917469f39b@spud \
--to=conor@kernel.org \
--cc=Alistair.Francis@wdc.com \
--cc=ajones@ventanamicro.com \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jrtc27@jrtc27.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oleksii.kurochko@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=qemu-riscv@nongnu.org \
--cc=rick@andestech.com \
--cc=robh+dt@kernel.org \
--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