From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add SoC IDs for the IPQ5210 family
Date: Wed, 18 Mar 2026 08:50:08 -0500 [thread overview]
Message-ID: <177384182867.14526.6866306623616746710.b4-ty@kernel.org> (raw)
In-Reply-To: <20260313-b4-ipq5210_soc_ids-v1-0-97faae3fef95@oss.qualcomm.com>
On Fri, 13 Mar 2026 21:32:55 +0530, Kathiravan Thirumoorthy wrote:
> SoCs based on IPQ5210 is shipped under 2 different marketing names such
> as Qualcomm Dragonwing F8 and Qualcomm Dragonwing N8. The difference being
> is F8 parts has the Passive Optical Network(PON) interface which acts as
> the backhaul where as in N8 parts it is ethernet backhaul.
>
> Add the SoC IDs for the same.
>
> [...]
Applied, thanks!
[1/2] dt-bindings: arm: qcom,ids: add SOC IDs for IPQ5210 family
commit: 508e58ac65eec4e272f89e39d9b64588f7fe21cc
[2/2] soc: qcom: socinfo: add SoC ID for IPQ5210 family
commit: 5a679430cf1def009b5c5cb821cad46be450c149
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-03-18 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 16:02 Kathiravan Thirumoorthy
2026-03-13 16:02 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: add SOC IDs for " Kathiravan Thirumoorthy
2026-03-14 10:42 ` Krzysztof Kozlowski
2026-03-13 16:02 ` [PATCH 2/2] soc: qcom: socinfo: add SoC ID " Kathiravan Thirumoorthy
2026-03-14 10:43 ` Krzysztof Kozlowski
2026-03-18 13:50 ` 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=177384182867.14526.6866306623616746710.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathiravan.thirumoorthy@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 \
/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®