From: sashiko-bot@kernel.org
To: "Yixun Lan" <dlan@kernel.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: power: spacemit: Add power domain controller
Date: Fri, 18 Sep 2026 02:43:53 +0000 [thread overview]
Message-ID: <20260918024354.7448D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918-04-k3-pm-support-v1-1-0acd2b36b96f@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] coding_style: incorrect SPDX comment style in C header file
--
commit 3ce4bb2badb48920b29e15de6dfdfcdbc013d6c4
Author: Yixun Lan <dlan@kernel.org>
dt-bindings: power: spacemit: Add power domain controller
This commit adds initial power domain driver support for the SpacemiT K1/K3
SoC. The controller is part of the APMU and manages power across multiple
power domains, including isolation and power-on sequences.
[ ... ]
> diff --git a/include/dt-bindings/power/spacemit,k3-power.h b/include/dt-bindings/power/spacemit,k3-power.h
> new file mode 100644
> index 0000000000000..54b39f2f09364
> --- /dev/null
> +++ b/include/dt-bindings/power/spacemit,k3-power.h
> @@ -0,0 +1,12 @@
> +// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
[Severity: Low]
This isn't a bug, but should this C header file use block comments (/* ... */)
for the SPDX license identifier?
According to the kernel licensing rules in Documentation/process/license-rules.rst,
C header files (.h) require block comments, while C++ style line comments (//)
are reserved for C source files (.c) and Device Tree sources.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918-04-k3-pm-support-v1-0-0acd2b36b96f@kernel.org?part=1
next prev parent reply other threads:[~2026-09-18 2:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 2:40 [PATCH 0/3] PM: spacemit: Add power domain support Yixun Lan
2026-09-18 2:40 ` [PATCH 1/3] dt-bindings: power: spacemit: Add power domain controller Yixun Lan
2026-09-18 2:43 ` sashiko-bot [this message]
2026-09-28 18:30 ` Rob Herring
2026-10-08 2:42 ` Yixun Lan
2026-09-18 2:40 ` [PATCH 2/3] pmdomain: spacemit: Add power domain driver Yixun Lan
2026-09-18 2:52 ` sashiko-bot
2026-09-18 9:00 ` Icenowy Zheng
2026-09-18 23:01 ` Yixun Lan
2026-09-19 6:57 ` Icenowy Zheng
2026-09-19 9:59 ` Yixun Lan
2026-09-19 13:56 ` Icenowy Zheng
2026-09-19 23:13 ` Yixun Lan
2026-09-20 5:17 ` Icenowy Zheng
2026-09-20 8:00 ` Troy Mitchell
2026-09-20 12:56 ` Icenowy Zheng
2026-09-21 3:35 ` Yixun Lan
2026-09-21 3:39 ` Icenowy Zheng
2026-09-21 12:43 ` Yixun Lan
2026-09-21 3:41 ` Icenowy Zheng
2026-09-21 12:44 ` Yixun Lan
2026-10-02 18:54 ` Iker Pedrosa
2026-10-04 13:47 ` Yixun Lan
2026-09-18 2:40 ` [PATCH 3/3] dts: riscv: spacemit: Add power domain nodes Yixun Lan
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=20260918024354.7448D1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@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