mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Neil Armstrong <neil.armstrong@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: qcom: sm8[456]50: add missing qcom,non-secure-domain property
Date: Mon, 18 Mar 2024 21:48:42 -0500	[thread overview]
Message-ID: <171081652642.198276.15833859282515233329.b4-ty@kernel.org> (raw)
In-Reply-To: <20240227-topic-sm8x50-upstream-fastrpc-non-secure-domain-v1-0-15c4c864310f@linaro.org>


On Tue, 27 Feb 2024 13:53:03 +0100, Neil Armstrong wrote:
> By default the DSP domains are non secure, add the missing
> qcom,non-secure-domain property to SM8450, SM8550 and SM8650
> in order to mark them as non-secure.
> 
> 

Applied, thanks!

[1/3] arm64: dts: qcom: sm8450: add missing qcom,non-secure-domain property
      commit: 033fbfa0eb60e519f50e97ef93baec270cd28a88
[2/3] arm64: dts: qcom: sm8550: add missing qcom,non-secure-domain property
      commit: 49c50ad9e6cbaa6a3da59cdd85d4ffb354ef65f4
[3/3] arm64: dts: qcom: sm8650: add missing qcom,non-secure-domain property
      commit: 039d379490eabf798baded4de2d698a7324ab7e6

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

      parent reply	other threads:[~2024-03-19  2:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 12:53 Neil Armstrong
2024-02-27 12:53 ` [PATCH 1/3] arm64: dts: qcom: sm8450: " Neil Armstrong
2024-02-27 12:53 ` [PATCH 2/3] arm64: dts: qcom: sm8550: " Neil Armstrong
2024-02-27 12:53 ` [PATCH 3/3] arm64: dts: qcom: sm8650: " Neil Armstrong
2024-03-19  2:48 ` 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=171081652642.198276.15833859282515233329.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@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®