From: Herbert Xu <herbert@gondor.apana.org.au>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Jia Jie Ho <jiajie.ho@starfivetech.com>,
"David S . Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Conor Dooley <conor@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v8 0/4] crypto: starfive - Add drivers for crypto engine
Date: Fri, 19 May 2023 17:29:32 +0800 [thread overview]
Message-ID: <ZGdBfPfL675OBcTS@gondor.apana.org.au> (raw)
In-Reply-To: <20230519-moodiness-backtalk-cc838c53e8b1@wendy>
On Fri, May 19, 2023 at 10:24:28AM +0100, Conor Dooley wrote:
>
> Can you drop the ea1aeba1b2e07b82f9eb7cce5cb169263a77d046 ("riscv: dts:
> starfive: Add crypto and DMA node for VisionFive 2") please?
> It depends on a clock node that has not been added to the dts yet, and
> will break the dtb build:
>
> Error: arch/riscv/boot/dts/starfive/jh7110.dtsi:505.22-23 syntax error
> FATAL ERROR: Unable to parse input tree
OK, I've dropped it.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2023-05-19 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 12:53 Jia Jie Ho
2023-05-15 12:53 ` [PATCH v8 1/4] dt-bindings: crypto: Add StarFive crypto module Jia Jie Ho
2023-05-15 12:53 ` [PATCH v8 2/4] crypto: starfive - Add crypto engine support Jia Jie Ho
2023-05-22 14:20 ` Conor Dooley
2023-05-15 12:53 ` [PATCH v8 3/4] riscv: dts: starfive: Add crypto and DMA node for VisionFive 2 Jia Jie Ho
2023-05-15 12:53 ` [PATCH v8 4/4] crypto: starfive - Add hash and HMAC support Jia Jie Ho
2023-05-19 8:50 ` [PATCH v8 0/4] crypto: starfive - Add drivers for crypto engine Herbert Xu
2023-05-19 9:24 ` Conor Dooley
2023-05-19 9:29 ` Herbert Xu [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=ZGdBfPfL675OBcTS@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jiajie.ho@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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
Powered by JetHome