From: ChiaEn Wu <chiaen_wu@richtek.com>
To: <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>, ChiaEn Wu <chiaen_wu@richtek.com>
Subject: [PATCH v3 0/2][next] Revise Richtek RT9467 documentation compatible name
Date: Fri, 17 Feb 2023 16:06:04 +0800 [thread overview]
Message-ID: <cover.1676648773.git.chiaen_wu@richtek.com> (raw)
This patch series revise Richtek RT9467 documentation compatible name from
"richtek,rt946-charger" to "richtek,rt9467" and rename the file name of rt9467
documentation yaml.
This issue was reported by Rob in this mail.
(https://lore.kernel.org/all/CAL_JsqJ4gueN3UFfea5JC6xfPjaH6a+7+dioTw=s0W-gBf6Anw@mail.gmail.com/)
Thank you,
ChiaEn Wu
ChiaEn Wu (2):
dt-bindings: power: supply: Revise Richtek RT9467 compatible name
dt-bindings: power: supply: Rename the file name of RT9467 charger
yaml
.../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
--
2.7.4
next reply other threads:[~2023-02-17 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 8:06 ChiaEn Wu [this message]
2023-02-17 8:06 ` [PATCH v3 1/2][next] dt-bindings: power: supply: Revise Richtek RT9467 compatible name 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
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=cover.1676648773.git.chiaen_wu@richtek.com \
--to=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).