Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Colin Huang via B4 Relay" <devnull+u8813345.gmail.com@kernel.org>
Cc: linux-hwmon@vger.kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: trivial-devices: Add Delta E50SN12051
Date: Fri, 08 May 2026 19:42:20 +0000	[thread overview]
Message-ID: <20260508194221.94438C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260508-add-e50sn12051-v5-1-abebdcc29665@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The new compatible string and its description comment are inserted incorrectly, resulting in mismatched descriptions for two devices.
--

commit 9996702d5ece9eeefae380c70a0a1d77e2a9cf5a
Author: Colin Huang <u8813345@gmail.com>

dt-bindings: trivial-devices: Add Delta E50SN12051
    
This commit adds the Delta E50SN12051 600W Non-isolated 1/8th Brick DC/DC
Power Module to the list of trivial devices.

> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
> index 23fd4513933a4..0f10368a13865 100644
> --- a/Documentation/devicetree/bindings/trivial-devices.yaml
> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml
> @@ -100,6 +100,8 @@ properties:
>              # Delta Electronics DPS920AB 920W 54V Power Supply
>            - delta,dps920ab
>              # 1/4 Brick DC/DC Regulated Power Module
> +          - delta,e50sn12051
> +            # 600W Non-isolated 1/8th Brick DC/DC Power Modules
>            - delta,q54sj108a2

This isn't a bug, but it looks like the comment and the compatible string
are inserted in the wrong order. In this file, comments describe the
compatible string that immediately follows them.

By inserting the new string before the new comment, the existing "1/4 Brick"
comment now appears to describe the new delta,e50sn12051 string, and the new
"600W" comment describes the existing delta,q54sj108a2 string. 

Should the new comment be placed above delta,e50sn12051 instead to keep the
descriptions aligned with their respective devices?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260508-add-e50sn12051-v5-0-abebdcc29665@gmail.com?part=1

  parent reply	other threads:[~2026-05-08 19:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  9:44 [PATCH v5 0/3] add support for Delta E50SN12051 Colin Huang via B4 Relay
2026-05-08  9:44 ` [PATCH v5 1/3] dt-bindings: trivial-devices: Add " Colin Huang via B4 Relay
2026-05-08 15:01   ` Conor Dooley
2026-05-08 19:42   ` sashiko-bot [this message]
2026-05-09 15:38   ` Guenter Roeck
2026-05-08  9:44 ` [PATCH v5 2/3] Documentation/hwmon: add Delta E50SN12051 documentation Colin Huang via B4 Relay
2026-05-09 15:40   ` Guenter Roeck
2026-05-08  9:44 ` [PATCH v5 3/3] hwmon: (pmbus) add support for Delta E50SN12051 Colin Huang via B4 Relay
2026-05-09 15:40   ` Guenter Roeck

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=20260508194221.94438C2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+u8813345.gmail.com@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox