linux-kernel - Re: [PATCH] regmap: allow const array for {devm_,}regmap_field_bulk_alloc reg

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: <162791623913.28098.17676239882362578796.b4-ty@kernel.org>
Date:   Mon,  2 Aug 2021 16:02:32 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Icenowy Zheng <icenowy@...eed.com>,
        "Rafael J . Wysocki" <rafael@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: allow const array for {devm_,}regmap_field_bulk_alloc reg_fields

On Mon, 2 Aug 2021 14:37:41 +0800, Icenowy Zheng wrote:
> The reg_fields array fed to {devm_}regmap_field_bulk_alloc is currently
> not const, which is not correct on semantics (the functions shouldn't
> change reg_field contents) and prevents pre-defined const reg_field
> array to be used.
> 
> As the implementation of this function doesn't change the content of it,
> just add const to its prototype.

Applied to

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

Thanks!

[1/1] regmap: allow const array for {devm_,}regmap_field_bulk_alloc reg_fields
      commit: 29c34975c9391d3ad1fd5dd3c92ba0d41afe9549

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