All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: lee@kernel.org, devicetree@vger.kernel.org,
	dmitry.torokhov@gmail.com, conor+dt@kernel.org,
	linux-leds@vger.kernel.org, linux-input@vger.kernel.org,
	robh@kernel.org
Subject: Re: [PATCH v7 1/6] dt-bindings: leds: leds-cpcap: convert to DT schema
Date: Tue, 21 Jul 2026 10:06:21 +0000	[thread overview]
Message-ID: <20260721100621.EB5EB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260721095654.429346-2-clamor95@gmail.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] The commit message description following the subsystem prefix is not capitalized.
- [Low] The newly added YAML binding points to a non-existent MFD schema, and the parent MFD binding still points to the deleted text file.
- [Low] The YAML binding conversion omitted the `examples` block.
--

--- Patch [1]: [PATCH v7 1/6] dt-bindings: leds: leds-cpcap: convert to DT schema ---
commit 42a8d75469150373ffb675f9ae6fccd8e3d482d6
Author: Svyatoslav Ryhel <clamor95@gmail.com>

dt-bindings: leds: leds-cpcap: convert to DT schema

Convert LEDs devicetree bindings for the Motorola CPCAP MFD from TXT to
YAML format. This patch does not change any functionality; the bindings
remain the same.

> dt-bindings: leds: leds-cpcap: convert to DT schema

[Severity: Low]
This isn't a bug, but should the description following the subsystem prefix
be capitalized? The LED subsystem conventions typically expect a capitalized
description, such as "Convert to DT schema".

> diff --git a/Documentation/devicetree/bindings/leds/motorola,cpcap-leds.yaml b/Documentation/devicetree/bindings/leds/motorola,cpcap-leds.yaml
> new file mode 100644
> index 0000000000000..c8e7b88a05ccf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/motorola,cpcap-leds.yaml

[ ... ]

> +description:
> +  This module is part of the Motorola CPCAP MFD device. For more details
> +  see Documentation/devicetree/bindings/mfd/motorola,cpcap.yaml. LEDs are
> +  represented as sub-nodes of the PMIC node on the device tree.

[Severity: Low]
Does motorola,cpcap.yaml exist yet? It looks like this references a
non-existent MFD schema. Additionally, the parent MFD binding in
Documentation/devicetree/bindings/mfd/motorola-cpcap.txt wasn't updated
to reflect the deletion of the old leds-cpcap.txt file.

[ ... ]

> +required:
> +  - compatible
> +  - label
> +  - vdd-supply
> +
> +unevaluatedProperties: false
> +
> +...

[Severity: Low]
Should this YAML file include an examples block? The YAML conversion
drops the original usage example from the .txt file. 

Running dt_binding_check on standalone schemas that lack an examples section
can result in warnings or incomplete schema validation.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260721095654.429346-1-clamor95@gmail.com?part=1

  reply	other threads:[~2026-07-21 10:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  9:56 [PATCH v7 0/6] mfd: cpcap: convert documentation to schema and add Mot board support Svyatoslav Ryhel
2026-07-21  9:56 ` [PATCH v7 1/6] dt-bindings: leds: leds-cpcap: convert to DT schema Svyatoslav Ryhel
2026-07-21 10:06   ` sashiko-bot [this message]
2026-07-21 12:01   ` Rob Herring (Arm)
2026-07-21  9:56 ` [PATCH v7 2/6] dt-bindings: input: cpcap-pwrbutton: " Svyatoslav Ryhel
2026-07-21 10:08   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 3/6] dt-bindings: mfd: motorola-cpcap: " Svyatoslav Ryhel
2026-07-21 10:15   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 4/6] dt-bindings: mfd: motorola-cpcap: document Mapphone and Mot CPCAP Svyatoslav Ryhel
2026-07-21 10:16   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 5/6] mfd: motorola-cpcap: diverge configuration per-board Svyatoslav Ryhel
2026-07-21 10:23   ` sashiko-bot
2026-07-21  9:56 ` [PATCH v7 6/6] mfd: motorola-cpcap: add support for Mot CPCAP composition Svyatoslav Ryhel
2026-07-21 10:20   ` sashiko-bot

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=20260721100621.EB5EB1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.