From: Palmer Dabbelt <palmer@dabbelt.com>
To: Conor Dooley <conor@kernel.org>
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 12:43:13 -0700 (PDT) [thread overview]
Message-ID: <mhng-9e03f021-961d-44f3-81c1-9c09abd3662b@palmer-ri-x1c9a> (raw)
In-Reply-To: <20230622-stipend-flashily-97917469f39b@spud>
On Thu, 22 Jun 2023 11:59:32 PDT (-0700), Conor Dooley wrote:
> 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.
Works for me, thanks.
>
> Cheers,
> Conor.
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Conor Dooley <conor@kernel.org>
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 12:43:13 -0700 (PDT) [thread overview]
Message-ID: <mhng-9e03f021-961d-44f3-81c1-9c09abd3662b@palmer-ri-x1c9a> (raw)
In-Reply-To: <20230622-stipend-flashily-97917469f39b@spud>
On Thu, 22 Jun 2023 11:59:32 PDT (-0700), Conor Dooley wrote:
> 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.
Works for me, thanks.
>
> Cheers,
> Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-22 19:43 UTC|newest]
Thread overview: 18+ 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 16:54 ` Conor Dooley
2023-06-08 17:49 ` Rob Herring
2023-06-08 17:49 ` Rob Herring
2023-06-08 18:05 ` Conor Dooley
2023-06-08 18:05 ` Conor Dooley
2023-06-09 14:03 ` Rob Herring
2023-06-09 14:03 ` Rob Herring
2023-06-09 14:20 ` Conor Dooley
2023-06-09 14:20 ` Conor Dooley
2023-06-22 18:25 ` Palmer Dabbelt
2023-06-22 18:25 ` Palmer Dabbelt
2023-06-22 18:59 ` Conor Dooley
2023-06-22 18:59 ` Conor Dooley
2023-06-22 19:43 ` Palmer Dabbelt [this message]
2023-06-22 19:43 ` Palmer Dabbelt
2023-07-03 15:02 ` Ben Dooks
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=mhng-9e03f021-961d-44f3-81c1-9c09abd3662b@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=Alistair.Francis@wdc.com \
--cc=ajones@ventanamicro.com \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.