All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Daniel Matyas" <matyasdaniel005@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: axis-fifo: Added missing binding
Date: Wed, 16 Sep 2026 20:20:38 +0000	[thread overview]
Message-ID: <20260916202039.1AB7F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916201253.483877-1-matyasdaniel005@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] dt-bindings: axis-fifo: typo in compatible string causes schema validation failure
- [Low] dt-bindings: axis-fifo: duplicate binding due to undeleted text file
--

commit 568433c34dce8d35f577a763a1632c2b7df8dc0b
Author: Daniel Matyas <matyasdaniel005@gmail.com>

dt-bindings: axis-fifo: Added missing binding
    
drivers/staging/axis-fifo/axis-fifo.txt file described how the
devicetree of the driver should look like. Convert it to .yaml file.
Issue found by checkpatch.

> drivers/staging/axis-fifo/axis-fifo.txt file described how the
> devicetree of the driver should look like. Convert it to .yaml file.

[Severity: Low]
Does this commit leave a duplicate binding in the tree?

The commit message mentions converting the axis-fifo.txt file to .yaml,
but the patch does not appear to delete drivers/staging/axis-fifo/axis-fifo.txt.

> diff --git a/Documentation/devicetree/bindings/axis-fifo/xlnx,axi-fifo-mm-s.yaml b/Documentation/devicetree/bindings/axis-fifo/xlnx,axi-fifo-mm-s.yaml
> new file mode 100644
> index 0000000000000..ef1e6bcf782d7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/axis-fifo/xlnx,axi-fifo-mm-s.yaml
[ ... ]
> +properties:
> +  compatible:
> +    enum:
> +      - xlnx,axis-fifo-mm-s-4.1
> +      - xlnx,axis-fifo-mm-s-4.2
> +      - xlnx,axis-fifo-mm-s-4.3

[Severity: Low]
Are these compatible strings misspelled?

The enum defines xlnx,axis-fifo-mm-s-4.1 with an 's' in axis, but the
actual compatible string used by the driver, existing device trees, and the
provided YAML example is xlnx,axi-fifo-mm-s-4.1 without the 's'. This
could cause a schema validation regression.

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

  reply	other threads:[~2026-09-16 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 20:11 [PATCH] dt-bindings: axis-fifo: Added missing binding Daniel Matyas
2026-09-16 20:20 ` sashiko-bot [this message]
2026-09-16 23:19 ` Rob Herring (Arm)
2026-09-17  6:29 ` Greg KH
2026-09-17  6:37 ` 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=20260916202039.1AB7F1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=matyasdaniel005@gmail.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 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.