From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Richard Acayan <mailingradian@gmail.com>
Subject: Re: (subset) [PATCH 0/3] SDM670 shared memory and socinfo
Date: Mon, 27 May 2024 22:32:21 -0500 [thread overview]
Message-ID: <171686715143.523693.6811535821413799635.b4-ty@kernel.org> (raw)
In-Reply-To: <20240524012023.318965-5-mailingradian@gmail.com>
On Thu, 23 May 2024 21:20:24 -0400, Richard Acayan wrote:
> This adds the smem region to the SDM670 device tree and adds the SDM670
> SoC ID to the socinfo driver. In addition to socinfo, the shared memory
> region is also used for SMP2P and the remote processors, but they are
> not added yet.
>
> Richard Acayan (3):
> dt-bindings: arm: qcom,ids: Add SoC ID for SDM670
> soc: qcom: socinfo: Add SDM670 SoC ID table entry
> arm64: dts: qcom: sdm670: add smem region
>
> [...]
Applied, thanks!
[3/3] arm64: dts: qcom: sdm670: add smem region
commit: 265d9989df5012adc5bec8e894dff0572c195a0c
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
next prev parent reply other threads:[~2024-05-28 3:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 1:20 [PATCH 0/3] SDM670 shared memory and socinfo Richard Acayan
2024-05-24 1:20 ` [PATCH 1/3] dt-bindings: arm: qcom,ids: Add SoC ID for SDM670 Richard Acayan
2024-05-24 15:25 ` Konrad Dybcio
2024-05-25 16:59 ` Krzysztof Kozlowski
2024-05-24 1:20 ` [PATCH 2/3] soc: qcom: socinfo: Add SDM670 SoC ID table entry Richard Acayan
2024-05-24 15:25 ` Konrad Dybcio
2024-05-24 1:20 ` [PATCH 3/3] arm64: dts: qcom: sdm670: add smem region Richard Acayan
2024-05-28 3:32 ` Bjorn Andersson [this message]
2024-05-28 14:13 ` (subset) [PATCH 0/3] SDM670 shared memory and socinfo 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=171686715143.523693.6811535821413799635.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mailingradian@gmail.com \
--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