From: Lee Jones <lee@kernel.org>
To: Luca Weiss <luca@z3ntu.xyz>
Cc: linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, afd@ti.com,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: mfd: qcom,spmi-pmic: rename extcon node name
Date: Mon, 7 Nov 2022 09:08:16 +0000 [thread overview]
Message-ID: <Y2jLAIQcthVLWU9e@google.com> (raw)
In-Reply-To: <20221031175717.942237-1-luca@z3ntu.xyz>
On Mon, 31 Oct 2022, Luca Weiss wrote:
> extcon is a Linux-specific name and shouldn't be a part of the dts. Make
> it be called usb-detect@ instead.
>
> Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> ---
> This patch builds on top of
> https://lore.kernel.org/linux-arm-msm/20221031173933.936147-1-luca@z3ntu.xyz/
> But could also be applied without, if conflicts are resolved.
>
> Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Same here. Only 1/3 received.
Can I take this on its own?
> diff --git a/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml b/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml
> index cf10d62ace54..14aa42057d6f 100644
> --- a/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml
> +++ b/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml
> @@ -123,10 +123,6 @@ patternProperties:
> - $ref: /schemas/power/supply/qcom,pm8941-charger.yaml#
> - $ref: /schemas/power/supply/qcom,pm8941-coincell.yaml#
>
> - "extcon@[0-9a-f]+$":
> - type: object
> - $ref: /schemas/extcon/qcom,pm8941-misc.yaml#
> -
> "gpio(s)?@[0-9a-f]+$":
> type: object
> $ref: /schemas/pinctrl/qcom,pmic-gpio.yaml#
> @@ -143,6 +139,10 @@ patternProperties:
> type: object
> $ref: /schemas/thermal/qcom,spmi-temp-alarm.yaml#
>
> + "^usb-detect@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/extcon/qcom,pm8941-misc.yaml#
> +
> "^usb-vbus-regulator@[0-9a-f]+$":
> type: object
> $ref: /schemas/regulator/qcom,usb-vbus-regulator.yaml#
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2022-11-07 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 17:57 [PATCH 1/3] dt-bindings: mfd: qcom,spmi-pmic: rename extcon node name Luca Weiss
2022-10-31 17:57 ` [PATCH 2/3] bindings: pm8941-misc: rename misc " Luca Weiss
2022-11-02 10:35 ` Neil Armstrong
2022-11-02 15:43 ` Luca Weiss
2022-11-02 16:28 ` Rob Herring
2022-11-02 16:28 ` Rob Herring
2022-10-31 17:57 ` [PATCH 3/3] ARM: dts: qcom: pm8941: " Luca Weiss
2022-11-02 10:36 ` Neil Armstrong
2022-11-02 16:27 ` [PATCH 1/3] dt-bindings: mfd: qcom,spmi-pmic: rename extcon " Rob Herring
2022-11-07 9:08 ` Lee Jones [this message]
2022-11-07 12:49 ` Luca Weiss
2022-11-08 1:27 ` (subset) " Bjorn Andersson
2022-11-16 14:05 ` 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=Y2jLAIQcthVLWU9e@google.com \
--to=lee@kernel.org \
--cc=afd@ti.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).