linux-kernel - Re: [RESEND 00/10] Fix a bunch of W=1 warnings in Regulator

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: <159318460834.3136.15198327802374358899.b4-ty@kernel.org>
Date:   Fri, 26 Jun 2020 16:16:48 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Lee Jones <lee.jones@...aro.org>, lgirdwood@...il.com
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND 00/10] Fix a bunch of W=1 warnings in Regulator

On Thu, 25 Jun 2020 20:16:58 +0100, Lee Jones wrote:
> Attempting to clean-up W=1 kernel builds, which are currently
> overwhelmingly riddled with niggly little warnings.
> 
> Resent to include patch contributors/maintainers/MLs.
> 
> Lee Jones (10):
>   regulator: consumer: Supply missing prototypes for 3 core functions
>   regulator: devres: Fix issues with kerneldoc headers
>   regulator: of_regulator: Add missing colon for rdev kerneldoc argument
>   regulator: dbx500-prcmu: Remove unused function
>     dbx500_regulator_testcase()
>   regulator: ab8500: Remove unused embedded struct expand_register
>   regulator: wm8350-regulator: Repair odd formatting in documentation
>   regulator: cpcap-regulator: Remove declared and set, but never used
>     variable 'ignore'
>   regulator: cpcap-regulator: Demote kerneldoc header to standard
>     comment
>   regulator: da9063-regulator: Fix .suspend 'initialized field
>     overwritten' warnings
>   regulator: max14577-regulator: Demote kerneldoc header to standard
>     comment
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[01/10] regulator: consumer: Supply missing prototypes for 3 core functions
        commit: da6690767cbd344998f36081815c85f3d467e78c
[02/10] regulator: devres: Fix issues with kerneldoc headers
        (no commit info)
[03/10] regulator: of_regulator: Add missing colon for rdev kerneldoc argument
        (no commit info)
[04/10] regulator: dbx500-prcmu: Remove unused function dbx500_regulator_testcase()
        commit: d3cc3dfcc20e72d537550dbeebbe4a8faa7c2606
[05/10] regulator: ab8500: Remove unused embedded struct expand_register
        commit: aeee55b76bfd100d2612f50d2f9526d760ee2e37
[06/10] regulator: wm8350-regulator: Repair odd formatting in documentation
        commit: 2f5add1e42165c7eb7e4367e1180ae76aa13d394
[07/10] regulator: cpcap-regulator: Remove declared and set, but never used variable 'ignore'
        commit: b89a5effb3345a484584cc2b090af62e1ecb0871
[08/10] regulator: cpcap-regulator: Demote kerneldoc header to standard comment
        commit: 7b804ce0c2e0bbf77b3a1d4b457520145822c496
[09/10] regulator: da9063-regulator: Fix .suspend 'initialized field overwritten' warnings
        (no commit info)
[10/10] regulator: max14577-regulator: Demote kerneldoc header to standard comment
        commit: 0c32f8aa0711af177248c2cba9cb105f18e0c9bb

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark