From: Bjorn Andersson <andersson@kernel.org>
To: 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>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Harshal Dev <harshal.dev@oss.qualcomm.com>
Cc: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
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>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: (subset) [PATCH v2 0/2] Add TRNG support for Glymur SoC
Date: Mon, 20 Jul 2026 12:21:01 -0500 [thread overview]
Message-ID: <178456806282.1732507.17127203162851359741.b4-ty@kernel.org> (raw)
In-Reply-To: <20260424-glymur_trng_enablement-v2-0-0603cbe68440@oss.qualcomm.com>
On Fri, 24 Apr 2026 14:05:06 +0530, Harshal Dev wrote:
> Document and add the device-tree node to enable TRNG for Glymur SoC.
>
>
Applied, thanks!
[2/2] arm64: dts: qcom: glymur: add TRNG node
commit: 5d7ebb1f36ad8a51f4e60819a8c5bddf04a8d1a2
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-07-20 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 8:35 Harshal Dev
2026-04-24 8:35 ` [PATCH v2 1/2] dt-bindings: crypto: qcom,prng: Document Glymur TRNG Harshal Dev
2026-05-05 9:25 ` Herbert Xu
2026-04-24 8:35 ` [PATCH v2 2/2] arm64: dts: qcom: glymur: add TRNG node Harshal Dev
2026-05-06 9:32 ` Kuldeep Singh
2026-05-18 8:36 ` Harshal Dev
2026-06-09 6:36 ` Harshal Dev
2026-06-18 11:58 ` Harshal Dev
2026-06-18 12:20 ` Konrad Dybcio
2026-07-07 5:34 ` Harshal Dev
2026-07-20 17:21 ` Bjorn Andersson [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=178456806282.1732507.17127203162851359741.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=harshal.dev@oss.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuldeep.singh@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 \
/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
all inboxes | Powered by JetHome®