From: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.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,
linux-kernel@vger.kernel.org, aiqun.yu@oss.qualcomm.com,
tingwei.zhang@oss.qualcomm.com, trilok.soni@oss.qualcomm.com,
yijie.yang@oss.qualcomm.com
Subject: Re: [PATCH 0/2] Add Qualcomm SM8850 socinfo
Date: Mon, 29 Sep 2025 13:54:13 +0800 [thread overview]
Message-ID: <6094ed8b-ddcd-462c-8753-06a1d58a9691@oss.qualcomm.com> (raw)
In-Reply-To: <ebxbhaaefuoemadcef5h4lxfw2k2hwkfe72aubctqb3tk2zdmp@p7ck45rd2hy7>
On 9/25/2025 10:38 AM, Dmitry Baryshkov wrote:
> On Wed, Sep 24, 2025 at 04:17:45PM -0700, Jingyi Wang wrote:
>> Add socinfo for Qualcomm SM8850 SoC.
>
> What is SM8850?
>
SM8850 is the soc id for Kaanapali, SKU numbers instead of codename
is used in this file, like QCS9100 for lemans, do you mean we should
add the info "kaanapali" in commit msg?
Thanks,
Jingyi
>>
>> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>> ---
>> Jingyi Wang (2):
>> dt-bindings: arm: qcom,ids: add SoC ID for SM8850
>> soc: qcom: socinfo: add SM8850 SoC ID
>>
>> drivers/soc/qcom/socinfo.c | 1 +
>> include/dt-bindings/arm/qcom,ids.h | 1 +
>> 2 files changed, 2 insertions(+)
>> ---
>> base-commit: ae2d20002576d2893ecaff25db3d7ef9190ac0b6
>> change-id: 20250917-knp-socid-f96f14a9640d
>>
>> Best regards,
>> --
>> Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>>
>
next prev parent reply other threads:[~2025-09-29 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 23:17 Jingyi Wang
2025-09-24 23:17 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: add SoC ID for SM8850 Jingyi Wang
2025-09-24 23:17 ` [PATCH 2/2] soc: qcom: socinfo: add SM8850 SoC ID Jingyi Wang
2025-09-25 2:38 ` [PATCH 0/2] Add Qualcomm SM8850 socinfo Dmitry Baryshkov
2025-09-29 5:54 ` Jingyi Wang [this message]
2025-09-29 9:37 ` Dmitry Baryshkov
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=6094ed8b-ddcd-462c-8753-06a1d58a9691@oss.qualcomm.com \
--to=jingyi.wang@oss.qualcomm.com \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.com \
/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®