linux-kernel - Re: [PATCH 0/3] W=1 loose ends for 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 for Android: free password hash cracker in your pocket

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

Message-Id: <159422763672.28837.17771120905724125938.b4-ty@kernel.org>
Date:   Wed, 08 Jul 2020 18:00:36 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Lee Jones <lee.jones@...aro.org>, lgirdwood@...il.com
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] W=1 loose ends for Regulator

On Wed, 8 Jul 2020 13:48:29 +0100, Lee Jones wrote:
> These either needed small fix-ups for a rebase.
> 
> Lee Jones (3):
>   regulator: devres: Fix issues with kerneldoc headers
>   regulator: of_regulator: Add missing colon for rdev kerneldoc argument
>   regulator: devres: Standardise on function documentation headers
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: devres: Fix issues with kerneldoc headers
      commit: 9565cccd64876dd1f8732fad3a04f8daa41fcef9
[2/3] regulator: of_regulator: Add missing colon for rdev kerneldoc argument
      commit: 45e8446e7a153a011ae099bb8c5657bb853c0ad0
[3/3] regulator: devres: Standardise on function documentation headers
      commit: a7c15187b391d7fe9903903475a94e5cd5b796d6

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