From: sashiko-bot@kernel.org
To: "Neo Chang" <YLCHANG2@nuvoton.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v7 1/2] ASoC: dt-bindings: nuvoton,nau8360: Add NAU83G60
Date: Tue, 04 Aug 2026 03:35:00 +0000 [thread overview]
Message-ID: <20260804033501.4229E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804032951.1069901-2-YLCHANG2@nuvoton.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The applied diff is missing multiple changes explicitly claimed in the v5 and v6 changelogs, indicating an outdated or incorrectly rebased patch version was submitted.
--
--- Patch [1]: [PATCH v7 1/2] ASoC: dt-bindings: nuvoton,nau8360: Add NAU83G60 ---
commit c8636e38cd00e42bd686aa15feae080b51b694e2
Author: Neo Chang <YLCHANG2@nuvoton.com>
ASoC: dt-bindings: nuvoton,nau8360: Add NAU83G60
Add device tree bindings documentation for the Nuvoton NAU83G60 audio
amplifier.
> Changes in v6:
> - Remove '|' from descriptions.
> - Add firmware-name in required.
> - Add "nuvoton,dsp-tx-slot-mapping" and "nuvoton,dsp-rx-slot-mapping" properties.
>
> Changes in v5:
> - Remove the detailed datasheet information, keep only the valid I2C address enum
> - Simplify the firmware firmware-name items definition by removing the redundant
> minItems/maxItems and moving the channel descriptions directly into individual
> item entries.
[Severity: Medium]
It appears this patch doesn't include the updates mentioned in the v5 and v6
changelogs. Was an older or incorrectly rebased version of the patch sent?
> diff --git a/Documentation/devicetree/bindings/sound/nuvoton,nau8360.yaml b/Documentation/devicetree/bindings/sound/nuvoton,nau8360.yaml
> new file mode 100644
> index 0000000000000..2d19aedf1419a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/nuvoton,nau8360.yaml
[ ... ]
> + firmware-name:
> + minItems: 2
> + maxItems: 2
> + description:
> + Assign firmware filenames for Left and Right DSP cores.
[Severity: Medium]
The v5 changelog states that the redundant minItems/maxItems were removed and
the channel descriptions were moved into individual item entries, but this block
still uses minItems and maxItems. Should this be updated to use an items list?
[ ... ]
> +required:
> + - compatible
> + - reg
> +
> +allOf:
[Severity: Medium]
The v6 changelog explicitly mentions adding firmware-name to the required list.
Additionally, the nuvoton,dsp-tx-slot-mapping and nuvoton,dsp-rx-slot-mapping
properties mentioned in the v6 changelog are completely absent from the file.
Are these missing from the submitted patch?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260804032951.1069901-1-YLCHANG2@nuvoton.com?part=1
next prev parent reply other threads:[~2026-08-04 3:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 3:29 [PATCH v7 0/2] ASoC: codecs: Add Nuvoton NAU83G60 audio codec driver Neo Chang
2026-08-04 3:29 ` [PATCH v7 1/2] ASoC: dt-bindings: nuvoton,nau8360: Add NAU83G60 Neo Chang
2026-08-04 3:35 ` sashiko-bot [this message]
2026-08-04 3:29 ` [PATCH v7 2/2] ASoC: codecs: nau8360: Add support for NAU83G60 amplifier Neo Chang
2026-08-04 3:44 ` sashiko-bot
2026-08-04 15:58 ` Mark Brown
2026-08-05 9:03 ` YLCHANG2
2026-08-05 10:30 ` Mark Brown
2026-08-05 11:34 ` YLCHANG2
2026-08-05 12:33 ` Mark Brown
2026-08-06 3:27 ` YLCHANG2
2026-08-06 11:41 ` Mark Brown
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=20260804033501.4229E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=YLCHANG2@nuvoton.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox