Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Harshal Dev <harshal.dev@oss.qualcomm.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: crypto: qcom,prng: document x1e80100
Date: Wed, 10 Dec 2025 06:44:24 +0100	[thread overview]
Message-ID: <bd5e550a-bd31-4785-ae95-f14b28c6ff7f@kernel.org> (raw)
In-Reply-To: <20251210-trng_dt_binding_x1e80100-v2-1-f678c6a44083@oss.qualcomm.com>

On 10/12/2025 06:36, Harshal Dev wrote:
> Document x1e80100 compatible for the True Random Number Generator.
> 
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Tested-by: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>


How did you test a binding? To remind - kernel tools and make is not
testing.

Best regards,
Krzysztof

  reply	other threads:[~2025-12-10  5:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10  5:36 [PATCH v2 0/2] Add TRNG node for x1e80100 SoC Harshal Dev
2025-12-10  5:36 ` [PATCH v2 1/2] dt-bindings: crypto: qcom,prng: document x1e80100 Harshal Dev
2025-12-10  5:44   ` Krzysztof Kozlowski [this message]
2025-12-10  7:00     ` Harshal Dev
2025-12-10  5:36 ` [PATCH v2 2/2] arm64: dts: qcom: x1e80100: add TRNG node Harshal Dev

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=bd5e550a-bd31-4785-ae95-f14b28c6ff7f@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=harshal.dev@oss.qualcomm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=wenjia.zhang@oss.qualcomm.com \
    /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