public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, agross@kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	andersson@kernel.org, bhupesh.linux@gmail.com,
	robh+dt@kernel.org, vladimir.zapolskiy@linaro.org,
	rfoss@kernel.org
Subject: Re: [PATCH 0/5] arm64: dts: qcom: Enable Crypto Engine for a few Qualcomm SoCs
Date: Wed, 22 Mar 2023 09:35:35 +0100	[thread overview]
Message-ID: <ea863eac-58bd-cd61-ce5c-a0393bb4e4a8@linaro.org> (raw)
In-Reply-To: <CAH=2NtziWx2g_4K92iH+9DLo8XV0P32NNnEpxy6f0G_dQOVs+Q@mail.gmail.com>

On 22/03/2023 09:33, Bhupesh Sharma wrote:
> On Wed, 22 Mar 2023 at 00:57, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
>>
>>
>>
>> On 21.03.2023 20:01, Bhupesh Sharma wrote:
>>> This patchset enables Crypto Engine support for Qualcomm SoCs like
>>> SM6115, SM8150, SM8250 and SM8350.
>>>
>>> While at it, also fix the compatible string for BAM DMA engine
>>> used in sdm845.dtsi
>>>
>>> Note that:
>>> - SM8250 crypto engine patch utilizes the work already done by myself and
>>>   Vladimir.
>>> - SM8350 crypto engine patch utilizes the work already done by Robert.
>>>
>>> This patchset depends on the dt-bindings patch which added support for
>>> SM6115 and QCS2290 SoCs:
>>> https://lore.kernel.org/linux-arm-msm/20230321184811.3325725-1-bhupesh.sharma@linaro.org/
>> You could have included that one here for easier tracking!
> 
> Err.. the dt-binding maintainers have been asking to split the
> dt-binding patches from
> the dts ones in the past. So, let's stick to that for now :)

For submissions? No, we did not.

Best regards,
Krzysztof


  parent reply	other threads:[~2023-03-22  8:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 19:01 [PATCH 0/5] arm64: dts: qcom: Enable Crypto Engine for a few Qualcomm SoCs Bhupesh Sharma
2023-03-21 19:01 ` [PATCH 1/5] arm64: dts: qcom: sdm845: Fix the BAM DMA engine compatible string Bhupesh Sharma
2023-03-21 19:29   ` Konrad Dybcio
2023-03-21 19:01 ` [PATCH 2/5] arm64: dts: qcom: sm6115: Add Crypto Engine support Bhupesh Sharma
2023-03-21 20:38   ` Stephan Gerhold
2023-03-22 10:41     ` Bhupesh Sharma
2023-03-21 19:01 ` [PATCH 3/5] arm64: dts: qcom: sm8150: " Bhupesh Sharma
2023-03-21 19:01 ` [PATCH 4/5] arm64: dts: qcom: sm8250: " Bhupesh Sharma
2023-03-21 19:01 ` [PATCH 5/5] arm64: dts: qcom: sm8350: " Bhupesh Sharma
2023-03-21 19:27 ` [PATCH 0/5] arm64: dts: qcom: Enable Crypto Engine for a few Qualcomm SoCs Konrad Dybcio
2023-03-22  8:33   ` Bhupesh Sharma
2023-03-22  8:34     ` Konrad Dybcio
2023-03-22  8:35     ` Krzysztof Kozlowski [this message]
2023-03-22 14:45 ` (subset) " 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=ea863eac-58bd-cd61-ce5c-a0393bb4e4a8@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhupesh.linux@gmail.com \
    --cc=bhupesh.sharma@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rfoss@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vladimir.zapolskiy@linaro.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