mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Val Packett <val@packett.cool>,
	Stephan Gerhold <stephan.gerhold@linaro.org>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Udit Tiwari <quic_utiwari@quicinc.com>,
	Neeraj Soni <quic_neersoni@quicinc.com>,
	Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v6] arm64: dts: qcom: x1e80100: Add crypto engine
Date: Thu, 18 Dec 2025 12:15:02 +0530	[thread overview]
Message-ID: <cd8946c5-3cee-4d43-9e49-f765dc965ece@oss.qualcomm.com> (raw)
In-Reply-To: <62930036-f817-4051-9657-46c1786287c5@kernel.org>



On 12/17/2025 7:23 PM, Krzysztof Kozlowski wrote:
> On 17/12/2025 14:53, Krzysztof Kozlowski wrote:
>> On 11/12/2025 09:49, Harshal Dev wrote:
>>> On X Elite, there is a crypto engine IP block similar to ones found on
>>> SM8x50 platforms.
>>>
>>> Describe the crypto engine and its BAM.
>>>
>>> Tested-by: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>
>>> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>> Reviewed-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>>> ---
>>> The dt-binding schema update for the x1e80100 compatible is here
>>> (already merged):
>>>     
>>> https://lore.kernel.org/all/20250213-dt-bindings-qcom-qce-x1e80100-v1-1-d17ef73a1c12@linaro.org/
>>> ---
>>> Changes in v6:
>>> - Added Reviewed-by tag from Abel.
>>> - Link to v5: https://lore.kernel.org/r/20251210-crypto_dt_node_x1e80100-v5-1-5ad22a869a56@oss.qualcomm.com
>>
>> You just sent it 7 days ago! Why new version? Please relax, and help out
> 
> s/7/1 day ago/
> 
>> by reviewing other patches on the mailing lists in order to relieve the
>> burden of maintainers and move your patches higher up the list.
>>

Apologies for this Krzysztof, I will take Konrad's advice here to not
unnecessary collect tags and resend the patch. Will also try to look into some
reviews and see where I can be of help. :)

Thanks,
Harshal

>>
>> Best regards,
>> Krzysztof
> 
> 
> Best regards,
> Krzysztof


  reply	other threads:[~2025-12-18  6:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11  8:49 Harshal Dev
2025-12-17 13:38 ` Konrad Dybcio
2025-12-17 13:53 ` Krzysztof Kozlowski
2025-12-17 13:53   ` Krzysztof Kozlowski
2025-12-18  6:45     ` Harshal Dev [this message]
2025-12-17 23:07 ` Bjorn Andersson

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=cd8946c5-3cee-4d43-9e49-f765dc965ece@oss.qualcomm.com \
    --to=harshal.dev@oss.qualcomm.com \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_neersoni@quicinc.com \
    --cc=quic_utiwari@quicinc.com \
    --cc=robh@kernel.org \
    --cc=stephan.gerhold@linaro.org \
    --cc=val@packett.cool \
    --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

all inboxes | Powered by JetHome®