From: Krzysztof Kozlowski <krzk@kernel.org>
To: 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>,
Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, rajendra.nayak@oss.qualcomm.com,
sibi.sankar@oss.qualcomm.com,
Jyothi Kumar Seerapu <jyothi.seerapu@oss.qualcomm.com>,
Maulik Shah <maulik.shah@oss.qualcomm.com>,
Taniya Das <taniya.das@oss.qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>,
Prudhvi Yarlagadda <quic_pyarlaga@quicinc.com>,
Qiang Yu <qiang.yu@oss.qualcomm.com>,
Manaf Meethalavalappu Pallikunhi
<manaf.pallikunhi@oss.qualcomm.com>,
Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>,
Abel Vesa <abelvesa@kernel.org>
Subject: Re: (subset) [PATCH v3 0/4] arm64: dts: qcom: Introduce Glymur SoC dtsi and Glymur CRD dts
Date: Mon, 23 Feb 2026 21:34:31 +0100 [thread overview]
Message-ID: <9009be77-8708-4403-b254-ebbd5aec103a@kernel.org> (raw)
In-Reply-To: <eijiiyxjtj6cw25gb3xaaeqitemtmrxeemcb52csoy34vw2wme@y22ajzhyfikm>
On 23/02/2026 21:31, Bjorn Andersson wrote:
> On Mon, Feb 23, 2026 at 01:56:10PM -0600, Bjorn Andersson wrote:
>>
>> On Fri, 19 Dec 2025 20:16:53 +0530, Pankaj Patil wrote:
>>> Introduce dt-bindings and initial device tree support for Glymur,
>>> Qualcomm's next-generation compute SoC and it's associated
>>> Compute Reference Device (CRD) platform.
>>>
>>> https://www.qualcomm.com/products/mobile/snapdragon/laptops-and-tablets/snapdragon-x2-elite
>>> https://www.qualcomm.com/news/releases/2025/09/new-snapdragon-x2-elite-extreme-and-snapdragon-x2-elite-are-the-
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/4] dt-bindings: arm: qcom: Document Glymur SoC and board
>> commit: 4ed5f35359db5fac587d4fb9f7f61c1c6f0729d7
>> [3/4] arm64: dts: qcom: Introduce Glymur base dtsi
>> commit: 41b6e8db400ccba9fc373ac3f0c9ebfd3a22c810
>> [4/4] arm64: dts: qcom: glymur: Enable Glymur CRD board support
>> commit: 9314c6ecace1a49aa40f75f72278e14d2feb2cd2
>>
>
> I don't know why b4 generated a ty message for this version, v8 has been
> merged.
I objected to the DTS patch.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-02-23 20:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 14:46 [PATCH v3 0/4] arm64: dts: qcom: Introduce Glymur SoC dtsi and Glymur CRD dts Pankaj Patil
2025-12-19 14:46 ` [PATCH v3 1/4] dt-bindings: arm: qcom: Document Glymur SoC and board Pankaj Patil
2025-12-19 14:46 ` [PATCH v3 2/4] arm64: defconfig: Enable Glymur configs for boot to shell Pankaj Patil
2025-12-19 14:57 ` Krzysztof Kozlowski
2025-12-20 17:14 ` Dmitry Baryshkov
2025-12-22 8:54 ` Pankaj Patil
2025-12-20 17:17 ` Dmitry Baryshkov
2025-12-22 10:24 ` Pankaj Patil
2025-12-19 14:46 ` [PATCH v3 3/4] arm64: dts: qcom: Introduce Glymur base dtsi Pankaj Patil
2025-12-20 18:46 ` Dmitry Baryshkov
2025-12-21 2:49 ` Dmitry Baryshkov
2025-12-21 15:17 ` Abel Vesa
2025-12-22 3:36 ` Bjorn Andersson
2025-12-22 9:10 ` Abel Vesa
2025-12-22 10:11 ` Kamal Wadhwa
2025-12-22 10:56 ` Stephan Gerhold
2025-12-30 8:02 ` Pankaj Patil
2025-12-30 14:30 ` Konrad Dybcio
2025-12-19 14:46 ` [PATCH v3 4/4] arm64: dts: qcom: glymur: Enable Glymur CRD board support Pankaj Patil
2025-12-20 18:48 ` Dmitry Baryshkov
2025-12-22 11:17 ` Stephan Gerhold
2025-12-30 14:45 ` Konrad Dybcio
2026-02-23 19:56 ` (subset) [PATCH v3 0/4] arm64: dts: qcom: Introduce Glymur SoC dtsi and Glymur CRD dts Bjorn Andersson
2026-02-23 20:31 ` Bjorn Andersson
2026-02-23 20:34 ` Krzysztof Kozlowski [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=9009be77-8708-4403-b254-ebbd5aec103a@kernel.org \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jishnu.prakash@oss.qualcomm.com \
--cc=jyothi.seerapu@oss.qualcomm.com \
--cc=kamal.wadhwa@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=manaf.pallikunhi@oss.qualcomm.com \
--cc=maulik.shah@oss.qualcomm.com \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=qiang.yu@oss.qualcomm.com \
--cc=quic_pyarlaga@quicinc.com \
--cc=rajendra.nayak@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.com \
--cc=taniya.das@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