From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
conor.dooley@microchip.com, jrtc27@jrtc27.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
paul.walmsley@sifive.com, aou@eecs.berkeley.edu, heiko@sntech.de,
ajones@ventanamicro.com, guoren@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] riscv,isa fixups
Date: Tue, 24 Jan 2023 22:40:18 +0000 [thread overview]
Message-ID: <167460001809.14719.16320756846682473720.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221205174459.60195-1-conor@kernel.org>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 5 Dec 2022 17:44:58 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> I noticed ~today~ while looking at the isa manual that I had not
> accounted for another couple of edge cases with my regex. As before, I
> think attempting to validate the canonical order for multiletter stuff
> makes no sense - but we should totally try to avoid false-positives for
> combinations that are known to be valid.
>
> [...]
Here is the summary with links:
- [v3,1/2] dt-bindings: riscv: fix underscore requirement for multi-letter extensions
https://git.kernel.org/riscv/c/ec64efc4966e
- [v3,2/2] dt-bindings: riscv: fix single letter canonical order
https://git.kernel.org/riscv/c/a943385aa801
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-01-24 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 17:44 [PATCH v3 0/2] riscv,isa fixups Conor Dooley
2022-12-05 17:44 ` [PATCH v3 1/2] dt-bindings: riscv: fix underscore requirement for multi-letter extensions Conor Dooley
2022-12-06 13:06 ` Rob Herring
2022-12-05 17:45 ` [PATCH v3 2/2] dt-bindings: riscv: fix single letter canonical order Conor Dooley
2022-12-06 13:07 ` Rob Herring
2023-01-06 18:27 ` [PATCH v3 0/2] riscv,isa fixups Palmer Dabbelt
2023-01-06 18:34 ` Conor Dooley
2023-01-24 22:40 ` 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=167460001809.14719.16320756846682473720.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=jrtc27@jrtc27.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.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