From: Conor Dooley <conor.dooley@microchip.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jia Jie Ho <jiajie.ho@starfivetech.com>,
Olivia Mackall <olivia@selenic.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
<linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] hwrng: starfive - Enable compile testing
Date: Fri, 27 Jan 2023 11:13:20 +0000 [thread overview]
Message-ID: <Y9Ox0M3fW7Lqr2P6@wendy> (raw)
In-Reply-To: <Y9OveVKTkX8cRhyP@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
On Fri, Jan 27, 2023 at 07:03:21PM +0800, Herbert Xu wrote:
> Enable compile testing for jh7110. Also remove the dependency on
> HW_RANDOM.
Checked, the latter is because the whole menu is wrapped in a if
HW_RANDOM, so seems fair to me!
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-27 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 1:54 [PATCH v5 0/3] hwrng: starfive: Add driver for TRNG module Jia Jie Ho
2023-01-17 1:54 ` [PATCH v5 1/3] dt-bindings: rng: Add StarFive " Jia Jie Ho
2023-01-17 1:54 ` [PATCH v5 2/3] hwrng: starfive - Add TRNG driver for StarFive SoC Jia Jie Ho
2023-01-27 11:03 ` [PATCH] hwrng: starfive - Enable compile testing Herbert Xu
2023-01-27 11:13 ` Conor Dooley [this message]
2023-01-31 7:28 ` JiaJie Ho
2023-01-17 1:54 ` [PATCH v5 3/3] riscv: dts: starfive: Add TRNG node for VisionFive 2 Jia Jie Ho
2023-03-15 1:45 ` Palmer Dabbelt
2023-07-01 21:53 ` Aurelien Jarno
2023-07-01 23:05 ` Conor Dooley
2023-07-03 7:52 ` Jia Jie Ho
2023-01-27 11:00 ` [PATCH v5 0/3] hwrng: starfive: Add driver for TRNG module Herbert Xu
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=Y9Ox0M3fW7Lqr2P6@wendy \
--to=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--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=olivia@selenic.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