linux-kernel - Re: [PATCH] regulator: core.c: Improve a comment

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

Message-Id: <161903035951.13561.14721623663345930224.b4-ty@kernel.org>
Date:   Wed, 21 Apr 2021 20:03:29 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Sebastian Fricke <sebastian.fricke@...teo.net>,
        linux-kernel@...r.kernel.org
Cc:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH] regulator: core.c: Improve a comment

On Wed, 21 Apr 2021 05:52:37 +0000, Sebastian Fricke wrote:
> s/regulator may on/regulator may already be enabled/
> s/or left on/or was left on/
> 
> The aim of this patch is to make the comment more readable and to make
> it clear, that this is about a regulator, that is already enabled instead
> of a regulator that may be switched on.

Applied to

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

Thanks!

[1/1] regulator: core.c: Improve a comment
      commit: 72241e3190f2be668d60493cf0343ec535357b5e

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