From: Krzysztof Kozlowski <krzk@kernel.org>
To: Samuel Kayode <samuel.kayode@savoirfairelinux.com>,
Lee Jones <lee@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Dmitry Torokho <dmitry.torokhov@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Robin Gong <yibin.gong@nxp.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-imx@nxp.com, linux-input@vger.kernel.org,
Abel Vesa <abelvesa@linux.com>, Abel Vesa <abel.vesa@nxp.com>,
Robin Gong <b38343@freescale.com>,
Enric Balletbo Serra <eballetbo@gmail.com>
Subject: Re: [PATCH v2 2/9] dt-bindings: regulator: add pf1550
Date: Sat, 17 May 2025 13:13:44 +0200 [thread overview]
Message-ID: <0a0f9e2a-cd70-4f61-8ffc-0c13e3396ada@kernel.org> (raw)
In-Reply-To: <7c8ceab2aa66bf221981f689025d0bd29df8d596.1747409892.git.samuel.kayode@savoirfairelinux.com>
On 16/05/2025 20:50, Samuel Kayode wrote:
> Add the DT binding document for pf1550 regulators.
>
> Signed-off-by: Samuel Kayode <samuel.kayode@savoirfairelinux.com>
> ---
> .../devicetree/bindings/regulator/pf1550.yaml | 35 +++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/pf1550.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/pf1550.yaml b/Documentation/devicetree/bindings/regulator/pf1550.yaml
> new file mode 100644
> index 000000000000..a684ab974496
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/pf1550.yaml
> @@ -0,0 +1,35 @@
> +# SPDX-License-Identifier: GPL-2.0
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/pf1550.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Regulators for PF1550 PMIC from NXP.
Same comments as for other patch.
> +
> +maintainers:
> + - Samuel Kayode <samuel.kayode@savoirfairelinux.com>
> +
> +description: |
> + This module is part of the PF1550 MFD device. For more details
> + see Documentation/devicetree/bindings/mfd/pf1550.yaml.
> +
> + The regulator controller is represented as a sub-node of the PMIC node
> + on the device tree.
> +
> + The device has three LDO regulators, three buck converters and a DDR
> + termination reference voltage.
> +
> +properties:
> + compatible:
> + const: fsl,pf1550-regulator
This looks not needed.
> +
> +patternProperties:
> + "^(LDO[1-3]|SW[1-3]|VREFADDR)$":
Node names are lowercase.
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> +
> +required:
> + - compatible
Missing blank line
> +additionalProperties: false
> +
> +...
<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
next prev parent reply other threads:[~2025-05-17 11:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 18:29 [PATCH v2 0/9] add support for pf1550 PMIC MFD-based drivers Samuel Kayode
2025-05-16 18:47 ` [PATCH v2 1/9] dt-bindings: power: supply: add pf1550 Samuel Kayode
2025-05-17 11:12 ` Krzysztof Kozlowski
2025-05-16 18:50 ` [PATCH v2 2/9] dt-bindings: regulator: " Samuel Kayode
2025-05-17 11:13 ` Krzysztof Kozlowski [this message]
2025-05-16 18:52 ` [PATCH v2 3/9] dt-bindings: input: " Samuel Kayode
2025-05-17 11:14 ` Krzysztof Kozlowski
2025-05-16 18:54 ` [PATCH v2 5/9] mfd: pf1550: add core mfd driver Samuel Kayode
2025-05-17 11:18 ` Krzysztof Kozlowski
2025-05-20 13:25 ` kernel test robot
2025-05-16 18:55 ` [PATCH v2 6/9] regulator: pf1550: add support for regulator Samuel Kayode
2025-05-17 20:13 ` kernel test robot
2025-05-16 18:57 ` [PATCH v2 7/9] input: pf1550: add onkey support Samuel Kayode
2025-05-16 22:55 ` Dmitry Torokhov
2025-05-21 21:00 ` Samuel Kayode
2025-05-18 16:03 ` kernel test robot
2025-05-16 18:58 ` [PATCH v2 8/9] power: supply: pf1550: add battery charger support Samuel Kayode
2025-05-17 11:20 ` Krzysztof Kozlowski
2025-05-16 18:59 ` [PATCH v2 9/9] MAINTAINERS: add an entry for pf1550 mfd driver Samuel Kayode
[not found] ` <8be1626f970c9fab8b50ae9ad45e0ddd88fa36bf.1747409892.git.samuel.kayode@savoirfairelinux.com>
[not found] ` <31542315-5ea1-4849-b2f9-686cabce914a@kernel.org>
2025-05-21 16:16 ` [PATCH v2 4/9] dt-bindings: mfd: add pf1550 Samuel Kayode
2025-05-21 16:22 ` 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=0a0f9e2a-cd70-4f61-8ffc-0c13e3396ada@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@nxp.com \
--cc=abelvesa@linux.com \
--cc=b38343@freescale.com \
--cc=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eballetbo@gmail.com \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=samuel.kayode@savoirfairelinux.com \
--cc=sre@kernel.org \
--cc=yibin.gong@nxp.com \
/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).