linux-kernel - Re: [PATCH] regulator: rt5133: Add RT5133 PMIC regulator Support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1dd13d22-b8c5-42af-8584-f123bd43db6c@kernel.org>
Date: Thu, 17 Jul 2025 16:41:07 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: jeff_chang@...htek.com, lgirdwood@...il.com, broonie@...nel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: rt5133: Add RT5133 PMIC regulator Support

On 17/07/2025 10:16, jeff_chang@...htek.com wrote:
> From: Jeff Chang <jeff_chang@...htek.com>
> 
> RT5133 is an intefrated chip. It includes 8 LDOs and 3 GPOs that
> can be used to drive output high/low purpose. The dependency of the
> GPO block is internally LDO1 Voltage. If LDO1 voltage output disabled,
> GPO cannot be used to drive output high. It need to pay more attention
> on the usage.
> 
> Signed-off-by: Jeff Chang <jeff_chang@...htek.com>
> ---
>  .../bindings/regulator/richtek,rt5133.yaml    | 164 +++++

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.

<form letter>
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.
</form letter>

...

> +
> +static const struct of_device_id __maybe_unused rt5133_ofid_tbls[] = {
> +	{ .compatible = "richtek,rt5133", },
> +	{ }
> +};
> +MODULE_DEVICE_TABLE(of, rt5133_ofid_tbls);
> +
> +static struct i2c_driver rt5133_driver = {
> +	.driver = {
> +		.name = "rt5133",
> +		.owner = THIS_MODULE,

That's old template (like 12 yo one) you are using.

Maybe below will be helpful to find more of such artifacts:

Please run standard kernel tools for static analysis, like coccinelle,
smatch and sparse, and fix reported warnings. Also please check for
warnings when building with W=1. Most of these commands (checks or W=1
build) can build specific targets, like some directory, to narrow the
scope to only your code. The code here looks like it needs a fix. Feel
free to get in touch if the warning is not clear.

Best regards,
Krzysztof