linux-kernel - Re: [PATCH v2 00/10] regulator: kerneldoc section fixes

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZtBvepC8yjNtY0g-@smile.fi.intel.com>
Date: Thu, 29 Aug 2024 15:54:18 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Chen-Yu Tsai <wenst@...omium.org>
Cc: Mark Brown <broonie@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 00/10] regulator: kerneldoc section fixes

On Thu, Aug 29, 2024 at 04:51:20PM +0800, Chen-Yu Tsai wrote:
> Hi,
> 
> This is v2 of my regulator kerneldoc fixes series. The series sort of
> came as a request from Andy to not move code that already had warnings
> without fixing said warnings. So here I'm fixing them first.

> The bulk of the fixes are in the regulator core and OF code, but I also
> fixed up a few bits in common code that were missing "Return" sections.
> There's also a final patch to align terminology around "negative error
> number" within the regulator subsystem. These are purely kerneldoc and
> comment fixes and don't touch any actual code. I left the devres code
> and helpers alone for now.

> The patch series is based on next-20240829.

Instead of or in addition to this, please use --base parameter when formatting
patch series.

> Please merge if possible.
> I will rebase my I2C OF component prober series [1] on top of them.

Briefly looked again and all seems all right with some nit-picks, that I have
already sent individually.

Since Mark acknowledged English, I believe it's fine to go.

Reported-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>

-- 
With Best Regards,
Andy Shevchenko