linux-kernel - Re: [PATCH 0/2] regulator/qcom: Constify static structs

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]

Date:   Wed, 01 Jul 2020 23:24:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     agross@...nel.org, Rikard Falkeborn <rikard.falkeborn@...il.com>,
        bjorn.andersson@...aro.org
Cc:     lgirdwood@...il.com, linux-kernel@...r.kernel.org,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 0/2] regulator/qcom: Constify static structs

On Mon, 29 Jun 2020 21:46:30 +0200, Rikard Falkeborn wrote:
> Constify some static structs to allow the compiler to put them in
> read-only memory.
> 
> Rikard Falkeborn (2):
>   regulator: qcom_rpm: Constify struct regulator_ops
>   regulator: qcom_spmi: Constify struct regulator_ops
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: qcom_rpm: Constify struct regulator_ops
      commit: 8d41df6469eec8d784137aeeebf87dca7460ce37
[2/2] regulator: qcom_spmi: Constify struct regulator_ops
      commit: 3b619e3e2d1a89f383a0a0c527818dcb2bc66f92

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