From: Bjorn Andersson <andersson@kernel.org>
To: agross@kernel.org, konrad.dybcio@linaro.org, lee@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, Mukesh Ojha <quic_mojha@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v2 1/4] dt-bindings: mfd: qcom,tcsr: Add compatible for sm8250/sm8350
Date: Thu, 7 Dec 2023 18:57:50 -0800 [thread overview]
Message-ID: <170200426910.2871025.1931459275540622967.b4-ty@kernel.org> (raw)
In-Reply-To: <1698253601-11957-1-git-send-email-quic_mojha@quicinc.com>
On Wed, 25 Oct 2023 22:36:38 +0530, Mukesh Ojha wrote:
> Document the compatible for both sm8250 and sm8350 SoCs.
>
>
Applied, thanks!
[2/4] arm64: dts: qcom: sm8250: Add TCSR halt register space
commit: d59653233e8779e3fe082eb5635b9785f2095af6
[3/4] arm64: dts: qcom: sm8350: Add TCSR halt register space
commit: 1accc6031d925c6045c4776d5f3646996b0b242a
[4/4] arm64: dts: qcom: sm8550: Enable download mode register write
commit: 44b1f64cad5703c87918cc9ffbf9b79bb959418d
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
next prev parent reply other threads:[~2023-12-08 2:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 17:06 [PATCH v2 1/4] dt-bindings: mfd: qcom,tcsr: Add compatible for sm8250/sm8350 Mukesh Ojha
2023-10-25 17:06 ` [PATCH v2 2/4] arm64: dts: qcom: sm8250: Add TCSR halt register space Mukesh Ojha
2023-10-25 17:59 ` Dmitry Baryshkov
2023-10-25 17:06 ` [PATCH v2 3/4] arm64: dts: qcom: sm8350: " Mukesh Ojha
2023-10-25 17:59 ` Dmitry Baryshkov
2023-10-25 17:06 ` [PATCH v2 4/4] arm64: dts: qcom: sm8550: Enable download mode register write Mukesh Ojha
2023-11-23 14:07 ` Mukesh Ojha
2023-10-28 9:19 ` [PATCH v2 1/4] dt-bindings: mfd: qcom,tcsr: Add compatible for sm8250/sm8350 Krzysztof Kozlowski
2023-11-23 10:33 ` (subset) " Lee Jones
2023-12-08 2:57 ` Bjorn Andersson [this message]
2023-12-11 8:06 ` Mukesh Ojha
2023-12-11 10:46 ` Mukesh Ojha
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=170200426910.2871025.1931459275540622967.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=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@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