From: Conor Dooley <conor@kernel.org>
To: Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jia Jie Ho <jiajie.ho@starfivetech.com>
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] riscv: dts: starfive - Add crypto and trng node
Date: Wed, 9 Aug 2023 19:46:24 +0100 [thread overview]
Message-ID: <20230809-boogieman-kiwi-4528c4b925d7@spud> (raw)
In-Reply-To: <20230808141558.296631-1-jiajie.ho@starfivetech.com>
From: Conor Dooley <conor.dooley@microchip.com>
On Tue, 08 Aug 2023 22:15:56 +0800, Jia Jie Ho wrote:
> The following patches add hardware cryptographic and trng module nodes
> to JH7110 dts. Patches have been tested on VisionFive2 board.
>
> v2 - Fixed dtbs_check errors on dma node in patch 1. (Conor)
>
> Jia Jie Ho (2):
> riscv: dts: starfive - Add crypto and DMA node for JH7110
> riscv: dts: starfive - Add hwrng node for JH7110 SoC
>
> [...]
Applied to riscv-dt-for-next, thanks!
[1/2] riscv: dts: starfive - Add crypto and DMA node for JH7110
https://git.kernel.org/conor/c/e2c07765e179
[2/2] riscv: dts: starfive - Add hwrng node for JH7110 SoC
https://git.kernel.org/conor/c/87ddf5b10964
Thanks,
Conor.
prev parent reply other threads:[~2023-08-09 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 14:15 [PATCH v2 0/2] riscv: dts: starfive - Add crypto and trng node Jia Jie Ho
2023-08-08 14:15 ` [PATCH v2 1/2] riscv: dts: starfive - Add crypto and DMA node for JH7110 Jia Jie Ho
2023-08-08 14:15 ` [PATCH v2 2/2] riscv: dts: starfive - Add hwrng node for JH7110 SoC Jia Jie Ho
2023-08-09 18:46 ` Conor Dooley [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=20230809-boogieman-kiwi-4528c4b925d7@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jiajie.ho@starfivetech.com \
--cc=kernel@esmil.dk \
--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;
as well as URLs for NNTP newsgroup(s).