linux-kernel - Re: [PATCH] regulator: qcom: labibb: 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <160159243691.44970.9154350525275171802.b4-ty@kernel.org>
Date:   Thu, 01 Oct 2020 23:47:16 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Rikard Falkeborn <rikard.falkeborn@...il.com>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-arm-msm@...r.kernel.org, Andy Gross <agross@...nel.org>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        Nisha Kumari <nishakumari@...eaurora.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: qcom: labibb: Constify static structs

On Wed, 30 Sep 2020 18:26:02 +0200, Rikard Falkeborn wrote:
> The only usage of qcom_labibb_ops is to assign it to the ops field in
> the regulator_desc struct, which is a const pointer. The only usage of
> pmi8998_lab_desc and pmi8998_ibb_desc is to assign their address to the
> desc field in the labibb_regulator_data struct which can be made const,
> since it is only copied into the desc field in the
> labbibb_regulator_data struct. This struct is modified, but that's a
> copy of the static one. Make them const to allow the compiler to put
> them in read-only memory.

Applied to

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

Thanks!

[1/1] regulator: qcom: labibb: Constify static structs
      commit: e6f5ff17ca96456deceef94cf2577012a9df737f

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