Message ID | 20200625163614.4001403-1-lee.jones@linaro.org (mailing list archive) |
---|---|
Headers | show |
Series | Fix a bunch of W=1 warnings in Regulator | expand |
On Thu, 25 Jun 2020 17:36:04 +0100, Lee Jones wrote: > Attempting to clean-up W=1 kernel builds, which are currently > overwhelmingly riddled with niggly little warnings. > > 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 local tree regulator-next Thanks! [1/7] regulator: consumer: Supply missing prototypes for 3 core functions commit: da6690767cbd344998f36081815c85f3d467e78c [2/7] regulator: dbx500-prcmu: Remove unused function dbx500_regulator_testcase() commit: d3cc3dfcc20e72d537550dbeebbe4a8faa7c2606 [3/7] regulator: ab8500: Remove unused embedded struct expand_register commit: aeee55b76bfd100d2612f50d2f9526d760ee2e37 [4/7] regulator: wm8350-regulator: Repair odd formatting in documentation commit: 2f5add1e42165c7eb7e4367e1180ae76aa13d394 [5/7] regulator: cpcap-regulator: Remove declared and set, but never used variable 'ignore' commit: b89a5effb3345a484584cc2b090af62e1ecb0871 [6/7] regulator: cpcap-regulator: Demote kerneldoc header to standard comment commit: 7b804ce0c2e0bbf77b3a1d4b457520145822c496 [7/7] 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