linux-kernel - Re: [PATCH] regulator: max8893: Drop "

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: <168995069586.110341.5283976279358056645.b4-ty@kernel.org>
Date:   Fri, 21 Jul 2023 15:44:55 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Cc:     linux-kernel@...r.kernel.org, kernel@...gutronix.de
Subject: Re: [PATCH] regulator: max8893: Drop "_new" from probe callback

On Fri, 21 Jul 2023 09:33:03 +0200, Uwe Kleine-König wrote:
> The driver was introduced when .probe_new was the right probe callback
> to use for i2c drivers. Today .probe is the right one (again) and the
> driver was already switched in commit 964e186547b2 ("regulator: Switch
> i2c drivers back to use .probe()") but the name continued to include
> "_new". To prevent code readers wondering about what might be new here,
> drop that part of the name.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: max8893: Drop "_new" from probe callback
      commit: 813ebba3b100997a24984040673d35cb2dc9f418

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