devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jia Jie Ho <jiajie.ho@starfivetech.com>
Cc: 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>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv: dts: starfive - Add crypto and trng node
Date: Tue, 8 Aug 2023 08:13:59 +0100	[thread overview]
Message-ID: <20230808-despair-calm-40ca60de2afb@spud> (raw)
In-Reply-To: <20230808061150.81491-1-jiajie.ho@starfivetech.com>

[-- Attachment #1: Type: text/plain, Size: 423 bytes --]

On Tue, Aug 08, 2023 at 02:11:48PM +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.
> 
> Best regards,
> Jia Jie
> 
> Jia Jie Ho (2):
>   riscv: dts: starfive - Add crypto and DMA node for JH7110

>   riscv: dts: starfive - Add hwrng node for JH7110 SoC

I only got one patch, where is the other?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-08-08 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  6:11 [PATCH 0/2] riscv: dts: starfive - Add crypto and trng node Jia Jie Ho
2023-08-08  6:11 ` [PATCH 1/2] riscv: dts: starfive - Add crypto and DMA node for JH7110 Jia Jie Ho
2023-08-08  7:16   ` Conor Dooley
2023-08-08  7:38     ` Jia Jie Ho
2023-08-08  7:13 ` Conor Dooley [this message]
2023-08-08 10:17   ` [PATCH 0/2] riscv: dts: starfive - Add crypto and trng node JiaJie Ho
2023-08-08 10:44     ` Conor Dooley

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=20230808-despair-calm-40ca60de2afb@spud \
    --to=conor@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --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).