public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
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>,
	Georgi Djakov <djakov@kernel.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@linaro.org>,
	James Clark <james.clark@linaro.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Leo Yan <leo.yan@linux.dev>, David Heidelberg <david@ixit.cz>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, coresight@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 01/11] Revert "dt-bindings: mfd: syscon: Add qcom,apq8064-mmss-sfpb"
Date: Wed, 30 Apr 2025 10:07:38 +0100	[thread overview]
Message-ID: <20250430090738.GE1567507@google.com> (raw)
In-Reply-To: <20250425-fix-nexus-4-v3-1-da4e39e86d41@oss.qualcomm.com>

On Fri, 25 Apr 2025, Dmitry Baryshkov wrote:

> For some reason Lee has mis-squashed two commits, picking up one chunk
> from the first patch and one chunk from the second one. Rather than
> trying to fix it, revert commit 2c8de7df7418 ("dt-bindings: mfd: syscon:
> Add qcom,apq8064-mmss-sfpb").

Ah yes.  Looks like I took patch 5 before patch 4, then fudged the
conflict resolution.  No need to submit a revert, I have removed the
patch.

> Fixes: 2c8de7df7418 ("dt-bindings: mfd: syscon: Add qcom,apq8064-mmss-sfpb")
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
>  Documentation/devicetree/bindings/mfd/syscon.yaml | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index 71741f06d2fddd2d4fb6b69c1cfd2d449ce73f64..c6bbb19c3e3e2245b4a823df06e7f361da311000 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -98,7 +98,6 @@ select:
>            - mstar,msc313-pmsleep
>            - nuvoton,ma35d1-sys
>            - nuvoton,wpcm450-shm
> -          - qcom,apq8064-mmss-sfpb
>            - rockchip,px30-qos
>            - rockchip,rk3036-qos
>            - rockchip,rk3066-qos
> @@ -202,7 +201,6 @@ properties:
>            - mstar,msc313-pmsleep
>            - nuvoton,ma35d1-sys
>            - nuvoton,wpcm450-shm
> -          - qcom,apq8064-sps-sic
>            - rockchip,px30-qos
>            - rockchip,rk3036-qos
>            - rockchip,rk3066-qos
> 
> -- 
> 2.39.5
> 

-- 
Lee Jones [李琼斯]


  parent reply	other threads:[~2025-04-30  9:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25 17:47 [PATCH v3 00/11] ARM: qcom: fix APQ8064 schema warnings Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 01/11] Revert "dt-bindings: mfd: syscon: Add qcom,apq8064-mmss-sfpb" Dmitry Baryshkov
2025-04-28  7:07   ` Krzysztof Kozlowski
2025-04-28  7:09     ` Dmitry Baryshkov
2025-04-28  7:09     ` Krzysztof Kozlowski
2025-04-28 10:49       ` Dmitry Baryshkov
2025-04-28 17:50         ` Krzysztof Kozlowski
2025-04-29 12:23           ` Dmitry Baryshkov
2025-04-30  9:07   ` Lee Jones [this message]
2025-04-25 17:47 ` [PATCH v3 02/11] dt-bindings: mfd: syscon: add qcom,apq8064-mmss-sfpb Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 03/11] dt-bindings: mfd: syscon: add qcom,apq8064-sps-sic Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 04/11] dt-bindings: soc: qcom,rpm: add missing clock-controller node Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 05/11] dt-bindings: soc: qcom: qcom,rpm: add missing clock/-names properties Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 06/11] dt-bindings: arm: arm,coresight-static-replicator: add optional clocks Dmitry Baryshkov
2025-04-28  9:06   ` Suzuki K Poulose
2025-04-28 10:17     ` Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 07/11] ARM: dts: qcom: apq8064: add missing clocks to the timer node Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 08/11] ARM: dts: qcom: apq8064 merge hw splinlock into corresponding syscon device Dmitry Baryshkov
2025-04-25 17:47 ` [PATCH v3 09/11] ARM: dts: qcom: apq8064: use new compatible for SFPB device Dmitry Baryshkov
2025-04-25 19:49   ` Konrad Dybcio
2025-04-25 17:47 ` [PATCH v3 10/11] ARM: dts: qcom: apq8064: use new compatible for SPS SIC device Dmitry Baryshkov
2025-04-25 19:51   ` Konrad Dybcio
2025-04-25 17:47 ` [PATCH v3 11/11] ARM: dts: qcom: apq8064: move replicator out of soc node Dmitry Baryshkov
2025-04-29 17:53 ` [PATCH v3 00/11] (subset) ARM: qcom: fix APQ8064 schema warnings Suzuki K Poulose
2025-05-01 13:17 ` (subset) [PATCH v3 00/11] " Lee Jones

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=20250430090738.GE1567507@google.com \
    --to=lee@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=coresight@lists.linaro.org \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=james.clark@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=leo.yan@linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=robh@kernel.org \
    --cc=suzuki.poulose@arm.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