[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <83f60014-b32b-4a2b-9cd6-b0a03aa928d3@kernel.org>
Date: Sat, 17 May 2025 13:12:51 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Samuel Kayode <samuel.kayode@...oirfairelinux.com>,
Lee Jones <lee@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, Dmitry Torokhov
<dmitry.torokhov@...il.com>, Sebastian Reichel <sre@...nel.org>,
Robin Gong <yibin.gong@....com>
Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linux-imx@....com, linux-input@...r.kernel.org,
Abel Vesa <abelvesa@...ux.com>, Abel Vesa <abel.vesa@....com>,
Robin Gong <b38343@...escale.com>, Enric Balletbo Serra <eballetbo@...il.com>
Subject: Re: [PATCH v2 1/9] dt-bindings: power: supply: add pf1550
On 16/05/2025 20:47, Samuel Kayode wrote:
> Add the DT binding document for the battery charger module of pf1550.
>
> Signed-off-by: Samuel Kayode <samuel.kayode@...oirfairelinux.com>
> ---
> .../bindings/power/supply/pf1550_charger.yaml | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/power/supply/pf1550_charger.yaml
Filename matching compatible.
>
> diff --git a/Documentation/devicetree/bindings/power/supply/pf1550_charger.yaml b/Documentation/devicetree/bindings/power/supply/pf1550_charger.yaml
> new file mode 100644
> index 000000000000..10fc0b35917c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/supply/pf1550_charger.yaml
> @@ -0,0 +1,44 @@
> +# SPDX-License-Identifier: GPL-2.0
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/power/supply/pf1550_charger.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Battery charger driver for PF1550 PMIC from NXP.
Describe hardware, not driver.
Also drop full stop.
<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
</form letter>
Best regards,
Krzysztof
Powered by blists - more mailing lists