From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: ChiaEn Wu <chiaen_wu@richtek.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
sre@kernel.org
Cc: cy_huang@richtek.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
peterwu.pub@gmail.com
Subject: Re: [PATCH v3 2/2][next] dt-bindings: power: supply: Rename the file name of RT9467 charger yaml
Date: Fri, 17 Feb 2023 09:53:41 +0100 [thread overview]
Message-ID: <96ab36f1-5b74-1df1-c344-0936516fbf7d@linaro.org> (raw)
In-Reply-To: <ec1a341d5731977f3188997f3655e777becb881c.1676648773.git.chiaen_wu@richtek.com>
On 17/02/2023 09:06, ChiaEn Wu wrote:
> Rename the file name from "richtek,rt9467-charger.yaml" to
> "richtek,rt9467.yaml" to match the "compatible name".
>
> Fixes: e1b4620fb503 ("dt-bindings: power: supply: Add Richtek RT9467 battery charger")
> Signed-off-by: ChiaEn Wu <chiaen_wu@richtek.com>
> ---
> .../power/supply/richtek,rt9467-charger.yaml | 82 ----------------------
> .../bindings/power/supply/richtek,rt9467.yaml | 82 ++++++++++++++++++++++
> 2 files changed, 82 insertions(+), 82 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/power/supply/richtek,rt9467-charger.yaml
> create mode 100644 Documentation/devicetree/bindings/power/supply/richtek,rt9467.yaml
No improvements here. Please use standard Git tools or fix your
patch-handling-setup.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-02-17 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 8:06 [PATCH v3 0/2][next] Revise Richtek RT9467 documentation compatible name ChiaEn Wu
2023-02-17 8:06 ` [PATCH v3 1/2][next] dt-bindings: power: supply: Revise Richtek RT9467 " ChiaEn Wu
2023-02-17 8:53 ` Krzysztof Kozlowski
2023-02-17 8:06 ` [PATCH v3 2/2][next] dt-bindings: power: supply: Rename the file name of RT9467 charger yaml ChiaEn Wu
2023-02-17 8:53 ` Krzysztof Kozlowski [this message]
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=96ab36f1-5b74-1df1-c344-0936516fbf7d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterwu.pub@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).