public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Komal Bajaj <quic_kbajaj@quicinc.com>
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/2] arm64: dts: qcom: qdu1000: add IMEM
Date: Tue, 13 Jun 2023 15:30:29 -0700	[thread overview]
Message-ID: <168669542896.1315701.7413308610480150255.b4-ty@kernel.org> (raw)
In-Reply-To: <20230522151206.22654-1-quic_kbajaj@quicinc.com>

On Mon, 22 May 2023 20:42:04 +0530, Komal Bajaj wrote:
> Add IMEM on QDU1000 and QRU1000 SoCs.
> 
> Komal Bajaj (2):
>   dt-bindings: sram: qcom,imem: document qdu1000
>   arm64: dts: qcom: qdu1000: Add IMEM and PIL info region
> 
> .../devicetree/bindings/sram/qcom,imem.yaml         |  1 +
>  arch/arm64/boot/dts/qcom/qdu1000.dtsi               | 13 +++++++++++++
>  2 files changed, 14 insertions(+)
> 
> [...]

Applied, thanks!

[2/2] arm64: dts: qcom: qdu1000: Add IMEM and PIL info region
      commit: 21c9c7af1b37f3b38960f6abaf1b0b43f9db2467

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

      parent reply	other threads:[~2023-06-13 22:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 15:12 [PATCH 0/2] arm64: dts: qcom: qdu1000: add IMEM Komal Bajaj
2023-05-22 15:12 ` [PATCH 1/2] dt-bindings: sram: qcom,imem: document qdu1000 Komal Bajaj
2023-05-22 17:29   ` Conor Dooley
2023-05-22 15:12 ` [PATCH 2/2] arm64: dts: qcom: qdu1000: Add IMEM and PIL info region Komal Bajaj
2023-05-22 16:41   ` Konrad Dybcio
2023-06-13 22:30 ` 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=168669542896.1315701.7413308610480150255.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.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=quic_kbajaj@quicinc.com \
    --cc=robh+dt@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