From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
devicetree@vger.kernel.org, robh+dt@kernel.org, cyy@cyyself.name,
conor.dooley@microchip.com, krzysztof.kozlowski+dt@linaro.org,
paul.walmsley@sifive.com, ajones@ventanamicro.com
Subject: Re: [PATCH v3 0/7] ISA string parser cleanups
Date: Sun, 25 Jun 2023 23:20:23 +0000 [thread overview]
Message-ID: <168773522362.24181.16156078607515411409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230607-audacity-overhaul-82bb867a825f@spud>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 7 Jun 2023 21:28:24 +0100 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> With that out of the way, here are some cleanups for our riscv,isa
> handling.
>
> Here are some bits that were discussed with Drew on the "should we
> allow caps" threads that I have now created patches for:
> - splitting of riscv_of_processor_hartid() into two distinct functions,
> one for use purely during early boot, prior to the establishment of
> the possible-cpus mask & another to fit the other current use-cases
> - that then allows us to then completely skip some validation of the
> hartid in the parser
> - the biggest diff in the series is a rework of the comments in the
> parser, as I have mostly found the existing (sparse) ones to not be
> all that helpful whenever I have to go back and look at it
> - from writing the comments, I found a conditional doing a bit of a
> dance that I found counter-intuitive, so I've had a go at making that
> match what I would expect a little better
> - `i` implies 4 other extensions, so add them as extensions and set
> them for the craic. Sure why not like...
>
> [...]
Here is the summary with links:
- [v3,1/7] RISC-V: simplify register width check in ISA string parsing
https://git.kernel.org/riscv/c/fed14be476f0
- [v3,2/7] RISC-V: split early & late of_node to hartid mapping
https://git.kernel.org/riscv/c/2ac874343749
- [v3,3/7] RISC-V: validate riscv,isa at boot, not during ISA string parsing
https://git.kernel.org/riscv/c/069b0d517077
- [v3,4/7] RISC-V: rework comments in ISA string parser
https://git.kernel.org/riscv/c/6b913e3da87d
- [v3,5/7] RISC-V: remove decrement/increment dance in ISA string parser
https://git.kernel.org/riscv/c/7816ebc1ddd1
- [v3,6/7] dt-bindings: riscv: explicitly mention assumption of Zicntr & Zihpm support
https://git.kernel.org/riscv/c/1e5cae98e46d
- [v3,7/7] RISC-V: always report presence of extensions formerly part of the base ISA
https://git.kernel.org/riscv/c/07edc32779e3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-06-25 23:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 20:28 [PATCH v3 0/7] ISA string parser cleanups Conor Dooley
2023-06-07 20:28 ` [PATCH v3 1/7] RISC-V: simplify register width check in ISA string parsing Conor Dooley
2023-06-12 7:07 ` Sunil V L
2023-06-07 20:28 ` [PATCH v3 2/7] RISC-V: split early & late of_node to hartid mapping Conor Dooley
2023-06-12 7:31 ` Sunil V L
2023-06-07 20:28 ` [PATCH v3 3/7] RISC-V: validate riscv,isa at boot, not during ISA string parsing Conor Dooley
2023-06-12 7:33 ` Sunil V L
2023-06-07 20:28 ` [PATCH v3 4/7] RISC-V: rework comments in ISA string parser Conor Dooley
2023-06-07 20:28 ` [PATCH v3 5/7] RISC-V: remove decrement/increment dance " Conor Dooley
2023-06-12 7:52 ` Sunil V L
2023-06-07 20:28 ` [PATCH v3 6/7] dt-bindings: riscv: explicitly mention assumption of Zicntr & Zihpm support Conor Dooley
2023-06-14 23:02 ` Rob Herring
2023-06-07 20:28 ` [PATCH v3 7/7] RISC-V: always report presence of extensions formerly part of the base ISA Conor Dooley
2023-06-25 23:17 ` [PATCH v3 0/7] ISA string parser cleanups Palmer Dabbelt
2023-06-25 23:20 ` patchwork-bot+linux-riscv [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=168773522362.24181.16156078607515411409.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
/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 NNTP newsgroup(s).