linux-kernel - Re: [PATCH 0/5] drivers/regulator: Constify static variables

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: <160009510609.5653.5132281509197932767.b4-ty@kernel.org>
Date:   Mon, 14 Sep 2020 15:51:46 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Rikard Falkeborn <rikard.falkeborn@...il.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] drivers/regulator: Constify static variables

On Sun, 13 Sep 2020 10:41:09 +0200, Rikard Falkeborn wrote:
> Constify a couple of static variables, most importantly regulator_ops to
> allow the compiler to put them in read-only memory.
> 
> Rikard Falkeborn (5):
>   regulator: dummy: Constify dummy_initdata and dummy_ops
>   regulator: fixed: Constify static regulator_ops
>   regulator: stw481x-vmmc: Constify static structs
>   regulator: pca9450: Constify static regulator_ops
>   regulator: ti-abb: Constify ti_abb_reg_ops
> 
> [...]

Applied to

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

Thanks!

[1/5] regulator: dummy: Constify dummy_initdata and dummy_ops
      commit: 087c09c2d273823bac906d590280f7e8052f7eff
[2/5] regulator: fixed: Constify static regulator_ops
      commit: 96ee75ffd4f63a3d5f9d6a3ea592b2c0ee97acb0
[3/5] regulator: stw481x-vmmc: Constify static structs
      commit: 9032693e218e69a9527fd5d08c4ce5cdbe90820f
[4/5] regulator: pca9450: Constify static regulator_ops
      commit: 72f2746c52e3fa6c0f6740df2d4fb70419533084
[5/5] regulator: ti-abb: Constify ti_abb_reg_ops
      commit: 2b37a18b58ed12b711591ec54c2b2a0e2068cf6e

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