linux-kernel - Re: [PATCH 0/9] Fix a bunch more 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: <159318489845.4876.11953522362387911717.b4-ty@kernel.org>
Date:   Fri, 26 Jun 2020 16:21:38 +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: [PATCH 0/9] Fix a bunch more W=1 warnings in Regulator

On Fri, 26 Jun 2020 07:57:29 +0100, Lee Jones wrote:
> Attempting to clean-up W=1 kernel builds, which are currently
> overwhelmingly riddled with niggly little warnings.
> 
> This is the last of them.  Once applied, drivers/regulator will
> be clean of W=1 warnings.
> 
> Lee Jones (9):
>   regulator: max8998: Staticify internal function
>     max8998_get_current_limit()
>   regulator: qcom-rpmh-regulator: Repair dodgy kerneldoc header
>     formatting
>   regulator: pwm-regulator: Demote kerneldoc header to standard comment
>   regulator: stpmic1_regulator: Properly document 'struct
>     stpmic1_regulator_cfg'
>   regulator: tps65217-regulator: Remove pointless 'is unsigned int <0'
>     check
>   regulator: tps65217-regulator: Use the returned value of
>     tps65217_reg_read()
>   regulator: tps65218-regulator: Remove pointless 'is unsigned int <0'
>     check
>   regulator: wm8400-regulator: Repair dodgy kerneldoc header formatting
>   regulator: qcom_smd-regulator: Remove unused 'struct regulator_desc
>     pmi8994_boost'
> 
> [...]

Applied to

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

Thanks!

[1/9] regulator: max8998: Staticify internal function max8998_get_current_limit()
      commit: 36f69fa96a23a054d3aea5793ce2ef3d95907713
[2/9] regulator: qcom-rpmh-regulator: Repair dodgy kerneldoc header formatting
      commit: 7cb5f692077e3b91dcb706cbf58d495d066439ce
[3/9] regulator: pwm-regulator: Demote kerneldoc header to standard comment
      commit: 4e773e7392fb561eb4ae10deb526aa1ac8c13f61
[4/9] regulator: stpmic1_regulator: Properly document 'struct stpmic1_regulator_cfg'
      commit: ec84a7dff4474d0af6ef003719509e30aa93071d
[5/9] regulator: tps65217-regulator: Remove pointless 'is unsigned int <0' check
      commit: f10a5e499cf3e0978845cd85d8a375bcfa193907
[6/9] regulator: tps65217-regulator: Use the returned value of tps65217_reg_read()
      commit: 44455a6d3bcab53ae8330a009d513ade0f12c0c0
[7/9] regulator: tps65218-regulator: Remove pointless 'is unsigned int <0' check
      commit: 02d88863198c48675ceb2a244e5985c5650e5fe6
[8/9] regulator: wm8400-regulator: Repair dodgy kerneldoc header formatting
      commit: 0c5261663785b6505bf5d0f210f1ff0e4bd5ef2c
[9/9] regulator: qcom_smd-regulator: Remove unused 'struct regulator_desc pmi8994_boost'
      commit: bfa29acd18e53ff44135f2eae2b942419a8582cc

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