From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SM8650
Date: Mon, 30 Oct 2023 17:47:21 +0530 [thread overview]
Message-ID: <31ca9b01-d94d-71c2-bf2d-4786a20106bf@quicinc.com> (raw)
In-Reply-To: <20231030-topic-sm8650-upstream-socinfo-v2-1-4751e7391dc9@linaro.org>
On 10/30/2023 3:25 PM, Neil Armstrong wrote:
> Add the ID for the Qualcomm SM8650 SoC.
>
> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
-Mukesh
> ---
> include/dt-bindings/arm/qcom,ids.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
> index f7248348a459..51e0f6059410 100644
> --- a/include/dt-bindings/arm/qcom,ids.h
> +++ b/include/dt-bindings/arm/qcom,ids.h
> @@ -255,6 +255,7 @@
> #define QCOM_ID_SA8775P 534
> #define QCOM_ID_QRU1000 539
> #define QCOM_ID_QDU1000 545
> +#define QCOM_ID_SM8650 557
> #define QCOM_ID_SM4450 568
> #define QCOM_ID_QDU1010 587
> #define QCOM_ID_QRU1032 588
>
next prev parent reply other threads:[~2023-10-30 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 9:55 [PATCH v2 0/2] qcom: socinfo: Add SM8650 SoC ID table entry Neil Armstrong
2023-10-30 9:55 ` [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SM8650 Neil Armstrong
2023-10-30 12:17 ` Mukesh Ojha [this message]
2023-10-30 14:35 ` Krzysztof Kozlowski
2023-10-30 9:55 ` [PATCH v2 2/2] soc: qcom: socinfo: Add SM8650 SoC ID table entry Neil Armstrong
2023-10-30 12:22 ` Mukesh Ojha
2023-12-08 14:55 ` [PATCH v2 0/2] " 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=31ca9b01-d94d-71c2-bf2d-4786a20106bf@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@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=neil.armstrong@linaro.org \
--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