Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Thara Gopinath <thara.gopinath@gmail.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>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abhinaba Rakshit <quic_arakshit@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v2 0/2] Enable Qualcomm Crypto Engine for QCS615
Date: Tue, 13 May 2025 21:46:44 +0100	[thread overview]
Message-ID: <174716895382.39748.3928459424707589207.b4-ty@kernel.org> (raw)
In-Reply-To: <20250318-enable-qce-for-qcs615-v2-0-c5e05fe22572@quicinc.com>


On Tue, 18 Mar 2025 15:13:22 +0530, Abhinaba Rakshit wrote:
> Document QCS615 support for QCrypto driver and add QCE
> and Crypto BAM DMA nodes.
> 
> This patch series depends on the below patch series:
> https://lore.kernel.org/all/20241104-add_initial_support_for_qcs615-v5-0-9dde8d7b80b0@quicinc.com/ - Reviewed
> 
> 
> [...]

Applied, thanks!

[2/2] arm64: dts: qcom: qcs615: add QCrypto nodes
      commit: 4153eb38970a9f2328b01278c49b65fbdf84d4d2

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2025-05-13 20:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  9:43 [PATCH v2 0/2] Enable Qualcomm Crypto Engine for QCS615 Abhinaba Rakshit
2025-03-18  9:43 ` [PATCH v2 1/2] dt-bindings: crypto: qcom-qce: document QCS615 crypto engine Abhinaba Rakshit
2025-04-07  5:04   ` Herbert Xu
2025-03-18  9:43 ` [PATCH v2 2/2] arm64: dts: qcom: qcs615: add QCrypto nodes Abhinaba Rakshit
2025-04-01 16:40   ` Konrad Dybcio
2025-05-13 20:46 ` 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=174716895382.39748.3928459424707589207.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_arakshit@quicinc.com \
    --cc=robh@kernel.org \
    --cc=thara.gopinath@gmail.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