Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Petko Manolov" <petko.manolov@konsulko.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/3] dt-bindings: arm: altera: add Draeger M48 Module
Date: Fri, 11 Sep 2026 15:14:09 +0000	[thread overview]
Message-ID: <20260911151410.246031F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260911150755.2803736-3-petko.manolov@konsulko.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message erroneously describes the Draeger M48 CPU module as an NXP i.MX6 based board, but the bindings correctly place it under the Altera Cyclone 5 SoC platform.
--

commit 7e951377f9aeb640e72ba7c48aafcccf11752d1e
Author: Petko Manolov <petko.manolov@konsulko.com>

dt-bindings: arm: altera: add Draeger M48 Module

This commit adds a new device tree compatible string for the Draeger M48
CPU module to the Altera device tree bindings.

>     dt-bindings: arm: altera: add Draeger M48 Module
>     
>     Add DT compatible string for Draeger's M48 CPU Module, an i.MX6
>     based board.

[Severity: Medium]
Is the description of the board architecture accurate here? The commit message
states the hardware is an i.MX6 based board (an NXP architecture), but the
patch correctly adds the compatible string under properties:compatible:oneOf
in Documentation/devicetree/bindings/arm/altera.yaml, which places it under
the Altera Cyclone 5 platform bindings.

While a subsequent patch in the series confirms the board is indeed a Cyclone 5
device, it also repeats the same i.MX6 claim in its commit message.

Should this regression in the commit description be corrected to prevent
misleading architectural information from polluting the git history?

> diff --git a/Documentation/devicetree/bindings/arm/altera.yaml b/Documentation/devicetree/bindings/arm/altera.yaml
> index 3030cf46fe74c..8ed1ba7335103 100644
> --- a/Documentation/devicetree/bindings/arm/altera.yaml
> +++ b/Documentation/devicetree/bindings/arm/altera.yaml
> @@ -47,6 +47,7 @@ properties:
>            - enum:
>                - altr,socfpga-cyclone5-socdk
>                - denx,mcvevk
> +              - draeger,M48
>                - ebv,socrates
>                - macnica,sodia
>                - novtech,chameleon96

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260911150755.2803736-1-petko.manolov@konsulko.com?part=2

  reply	other threads:[~2026-09-11 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 15:07 [PATCH v4 0/3] arm: dts: altera: add Draeger M48 CPU Module Petko Manolov
2026-09-11 15:07 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: add Draeger AG Petko Manolov
2026-09-11 15:07 ` [PATCH v4 2/3] dt-bindings: arm: altera: add Draeger M48 Module Petko Manolov
2026-09-11 15:14   ` sashiko-bot [this message]
2026-09-13  9:18   ` Krzysztof Kozlowski
2026-09-13 13:32     ` Petko Manolov
2026-09-13 14:20       ` Krzysztof Kozlowski
2026-09-11 15:07 ` [PATCH v4 3/3] arm: dts: altera: add Draeger M48 CPU Module Petko Manolov
2026-09-11 15:18   ` 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=20260911151410.246031F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=petko.manolov@konsulko.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox