From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Dmitry Osipenko <digetx@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
David Heidelberg <david@ixit.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/4] dt-bindings: power: supply: qcom,pm8941: document usb-charge-current-limit
Date: Sun, 5 Jun 2022 17:26:03 -0500 [thread overview]
Message-ID: <20220605222603.GA3638715-robh@kernel.org> (raw)
In-Reply-To: <20220601071911.6435-3-krzysztof.kozlowski@linaro.org>
On Wed, 01 Jun 2022 09:19:10 +0200, Krzysztof Kozlowski wrote:
> Document already used (in DTS and by driver) 'usb-charge-current-limit'
> property:
>
> arch/arm/boot/dts/qcom-msm8974pro-fairphone-fp2.dtb:
> charger@1000: 'usb-charge-current-limit' does not match any of the regexes: 'pinctrl-[0-9]+'
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/power/supply/qcom,pm8941-charger.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-06-05 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 7:19 [PATCH 1/4] dt-bindings: power: supply: bq24190: use regulator schema for child node Krzysztof Kozlowski
2022-06-01 7:19 ` [PATCH 2/4] dt-bindings: power: supply: qcom,pm8941: " Krzysztof Kozlowski
2022-06-05 21:48 ` Rob Herring
2022-06-01 7:19 ` [PATCH 3/4] dt-bindings: power: supply: qcom,pm8941: document usb-charge-current-limit Krzysztof Kozlowski
2022-06-05 22:26 ` Rob Herring [this message]
2022-06-01 7:19 ` [PATCH 4/4] dt-bindings: power: supply: summit,smb347: use absolute path to schema Krzysztof Kozlowski
2022-06-02 15:47 ` David Heidelberg
2022-06-05 22:26 ` Rob Herring
2022-06-05 21:48 ` [PATCH 1/4] dt-bindings: power: supply: bq24190: use regulator schema for child node Rob Herring
2022-06-09 19:29 ` Sebastian Reichel
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=20220605222603.GA3638715-robh@kernel.org \
--to=robh@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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