linux-kernel - Re: [PATCH 0/8] regulator/tps*: Constify static regulator ops

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: <159897183313.47900.16357469471615056811.b4-ty@kernel.org>
Date:   Tue, 01 Sep 2020 15:50:38 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Rikard Falkeborn <rikard.falkeborn@...il.com>
Cc:     Tony Lindgren <tony@...mide.com>, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH 0/8] regulator/tps*: Constify static regulator ops

On Sun, 30 Aug 2020 00:10:56 +0200, Rikard Falkeborn wrote:
> Constify static instances of struct regulator_ops to allow the compiler
> to put them in read-only memory. Patches are independent. Compile-tested
> only.
> 
> Rikard Falkeborn (8):
>   regulator: tps51632: Constify tps51632_dcdc_ops
>   regulator: tps6105x: Constify tps6105x_regulator_ops
>   regulator: tps62360: Constify tps62360_dcdc_ops
>   regulator: tps65086: Constify static regulator_ops
>   regulator: tps65090: constify static regulator_ops
>   regulator: tps6586x: Constify static regulator_ops
>   regulator: tps65912: Constify static regulator_ops
>   regulator: tps65910: Constify static regulator_ops
> 
> [...]

Applied to

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

Thanks!

[1/8] regulator: tps51632: Constify tps51632_dcdc_ops
      commit: dcb97c10f967c2cfea4c6316f026bc4a4a165f1e
[2/8] regulator: tps6105x: Constify tps6105x_regulator_ops
      commit: 55c81934e7040c1e0c26b72ee752203ccf190b51
[3/8] regulator: tps62360: Constify tps62360_dcdc_ops
      commit: 01167e88e9372f9748e94a7322b0d43ccb980d9f
[4/8] regulator: tps65086: Constify static regulator_ops
      commit: 2e6d9db83ac7c65b986d3037620dc735dee7383f
[5/8] regulator: tps65090: constify static regulator_ops
      commit: 7d844ac3b5a8a97ae4a05d9f545346a4fca77cea
[6/8] regulator: tps6586x: Constify static regulator_ops
      commit: 25c8044502ca9fb684fe7a0612985069e27e01eb
[7/8] regulator: tps65912: Constify static regulator_ops
      commit: e92b8ef87a8a4a95056d6b5852bd4b5288f34540
[8/8] regulator: tps65910: Constify static regulator_ops
      commit: 385d41d7edbc37d6b30197672b744021ce3baccf

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