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, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, paul.walmsley@sifive.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dt-bindings: riscv: cpus: switch to unevaluatedProperties: false
Date: Sun, 25 Jun 2023 23:20:23 +0000 [thread overview]
Message-ID: <168773522373.24181.11034691970216052141.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230615-creamer-emu-ade0fa0bdb68@spud>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 15 Jun 2023 23:50:13 +0100 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Do the various bits needed to drop the additionalProperties: true that
> we currently have in riscv/cpu.yaml, to permit actually enforcing what
> people put in cpus nodes.
>
> Changes in v2:
> - drop patches 2 -> 5, they're now standard in dt-schema
>
> [...]
Here is the summary with links:
- [v2,1/2] dt-bindings: riscv: cpus: add a ref the common cpu schema
https://git.kernel.org/riscv/c/3c1b4758a954
- [v2,2/2] dt-bindings: riscv: cpus: switch to unevaluatedProperties: false
https://git.kernel.org/riscv/c/1ffe6ddc5c64
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: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 22:50 [PATCH v2 0/2] dt-bindings: riscv: cpus: switch to unevaluatedProperties: false Conor Dooley
2023-06-15 22:50 ` [PATCH v2 1/2] dt-bindings: riscv: cpus: add a ref the common cpu schema Conor Dooley
2023-06-20 16:48 ` Rob Herring
2023-06-15 22:50 ` [PATCH v2 2/2] dt-bindings: riscv: cpus: switch to unevaluatedProperties: false Conor Dooley
2023-06-20 16:48 ` Rob Herring
2023-06-20 17:00 ` [PATCH v2 0/2] " Palmer Dabbelt
2023-06-20 18:14 ` Conor Dooley
2023-06-25 23:17 ` 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=168773522373.24181.11034691970216052141.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--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