linux-kernel - Re: [PATCH] regmap: permit to set reg_update

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <165815182610.53791.17547202213321860152.b4-ty@kernel.org>
Date:   Mon, 18 Jul 2022 14:43:46 +0100
From:   Mark Brown <broonie@...nel.org>
To:     ansuelsmth@...il.com, linux-kernel@...r.kernel.org,
        rafael@...nel.org, gregkh@...uxfoundation.org
Subject: Re: [PATCH] regmap: permit to set reg_update_bits with bulk implementation

On Fri, 15 Jul 2022 22:10:32 +0200, Christian Marangi wrote:
> A regmap may still require to set a custom reg_update_bits instead of
> relying to the regmap_bus_read/write general function.
> 
> Permit to set it in the map if provided by the regmap config.
> 
> 

Applied to

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

Thanks!

[1/1] regmap: permit to set reg_update_bits with bulk implementation
      commit: 739f872e48d47c97fa17a86a7b3356771b75240c

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