From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anton Lundin <glance@ac2.se>, linux-hwmon@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>, Zev Weiss <zev@bewilderbeest.net>
Subject: Re: [PATCH] hwmon: (nct6775) Add support for NCT5525
Date: Tue, 3 Nov 2026 14:47:31 +0100 [thread overview]
Message-ID: <e1576fcc-b31b-4305-9145-7df0ecba5919@kernel.org> (raw)
In-Reply-To: <20261103132948.144216-1-glance@ac2.se>
On 03/11/2026 14:29, Anton Lundin wrote:
> Extend nct6775 driver to support NCT5525.
>
> Assisted-by: Copilot:GPT-5.6-Terra
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
> Signed-off-by: Anton Lundin <glance@ac2.se>
> ---
> .../bindings/hwmon/nuvoton,nct6775.yaml | 1 +
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
> Documentation/hwmon/nct6775.rst | 10 +-
> drivers/hwmon/nct6775-core.c | 130 +++++++++++++++++-
> drivers/hwmon/nct6775-i2c.c | 6 +-
> drivers/hwmon/nct6775-platform.c | 12 ++
> drivers/hwmon/nct6775.h | 3 +-
> 6 files changed, 156 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/hwmon/nuvoton,nct6775.yaml b/Documentation/devicetree/bindings/hwmon/nuvoton,nct6775.yaml
> index 244470282890..16c21f1f46ef 100644
> --- a/Documentation/devicetree/bindings/hwmon/nuvoton,nct6775.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/nuvoton,nct6775.yaml
> @@ -25,6 +25,7 @@ properties:
> - nuvoton,nct6797
> - nuvoton,nct6798
> - nuvoton,nct6799
> + - nuvoton,nct5525
Also, to spare you one review cycle - don't break the order.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-03 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 13:29 [PATCH] hwmon: (nct6775) Add support for NCT5525 Anton Lundin
2026-11-03 13:42 ` sashiko-bot
2026-11-03 13:47 ` Krzysztof Kozlowski [this message]
2026-11-03 15:06 ` Guenter Roeck
2026-11-03 17:33 ` Anton Lundin
2026-11-03 19:01 ` Guenter Roeck
2026-11-06 12:45 ` Anton Lundin
2026-11-06 13:50 ` Anton Lundin
2026-11-06 15:55 ` Guenter Roeck
2026-11-03 15:07 ` 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=e1576fcc-b31b-4305-9145-7df0ecba5919@kernel.org \
--to=krzk@kernel.org \
--cc=glance@ac2.se \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=zev@bewilderbeest.net \
/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