From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH 1/4] dt-bindings: arm: qcom-soc: Extend X1E prefix match for X1P
Date: Sat, 21 Dec 2024 21:39:03 +0100 [thread overview]
Message-ID: <9080f2ca-e350-4ac5-9021-3d277145dc0c@kernel.org> (raw)
In-Reply-To: <20241221-topic-x1p4_soc-v1-1-55347831d73c@oss.qualcomm.com>
On 21/12/2024 13:36, Konrad Dybcio wrote:
> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> The X1 series includes SoCs like X1P42100. Extend the pattern x1e match
> to x1[ep] to also include these.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> ---
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-21 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 12:35 [PATCH 0/4] X1P42100 bindings + common driver bits Konrad Dybcio
2024-12-21 12:36 ` [PATCH 1/4] dt-bindings: arm: qcom-soc: Extend X1E prefix match for X1P Konrad Dybcio
2024-12-21 20:39 ` Krzysztof Kozlowski [this message]
2024-12-21 12:36 ` [PATCH 2/4] dt-bindings: arm: qcom: Add X1P42100 SoC & CRD Konrad Dybcio
2024-12-21 20:39 ` Krzysztof Kozlowski
2024-12-21 12:36 ` [PATCH 3/4] soc: qcom: pd-mapper: Add X1P42100 Konrad Dybcio
2024-12-21 16:04 ` Dmitry Baryshkov
2024-12-21 12:36 ` [PATCH 4/4] firmware: qcom: scm: Allow QSEECOM on X1P42100 CRD Konrad Dybcio
2024-12-26 18:26 ` (subset) [PATCH 0/4] X1P42100 bindings + common driver bits 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=9080f2ca-e350-4ac5-9021-3d277145dc0c@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@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=marijn.suijten@somainline.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