[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ebdcd477-5f15-cc05-ec67-42369b23f5f1@linaro.org>
Date: Thu, 20 Jul 2023 11:00:20 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Hariharan K <quic_harihk@...cinc.com>, agross@...nel.org,
andersson@...nel.org, konrad.dybcio@...aro.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: quic_srichara@...cinc.com, quic_sjaganat@...cinc.com,
quic_kathirav@...cinc.com, quic_arajkuma@...cinc.com,
quic_anusha@...cinc.com
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: Document MP03.6-C2 board
based on IPQ5018 family
On 20/07/2023 09:57, Hariharan K wrote:
> Document the MP03.6-C2 (Reference Design Platform 434) board
> based on IPQ5018 family of SoCs.
>
> Signed-off-by: Hariharan K <quic_harihk@...cinc.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 922feb912594..2a18bb881624 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -98,6 +98,7 @@ description: |
> ap-mi01.6
> ap-mi01.9
> ap-mp03.5-c2
> + ap-mp03.6-c2
> cdp
> cp01-c1
> dragonboard
> @@ -344,6 +345,7 @@ properties:
> - items:
> - enum:
> - qcom,ipq5018-ap-mp03.5-c2
> + - qcom,ipq5018-ap-mp03.6-c2
Really, how do you see it being applied? You sent multiple conflicting
patches. Now, clone the kernel tree and use b4 to apply one patchset.
Then apply next one. Then next and next.
Did it succeed?
Best regards,
Krzysztof
Powered by blists - more mailing lists