linux-kernel - Re: [PATCH -next] regulator: max77857: change some variables to static

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: <169090886609.70332.15831728784398037433.b4-ty@kernel.org>
Date:   Tue, 01 Aug 2023 17:54:26 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Yang Yingliang <yangyingliang@...wei.com>
Cc:     lgirdwood@...il.com, okan.sahin@...log.com
Subject: Re: [PATCH -next] regulator: max77857: change some variables to
 static

On Tue, 01 Aug 2023 21:03:54 +0800, Yang Yingliang wrote:
> max77857_regmap_config and max77857_driver are only used
> in max77857-regulator.c now, change them to static.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: max77857: change some variables to static
      commit: 39b5ba6cb56962d2ac83e4dd89f68538f7861efe

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