linux-kernel - Re: [PATCH 0/3] remap: Some fixes for bulk read/write callbacks in regmap

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:   Mon, 20 Jun 2022 16:40:04 +0100
From:   Mark Brown <broonie@...nel.org>
To:     javierm@...hat.com, linux-kernel@...r.kernel.org
Cc:     marex@...x.de, rafael@...nel.org, gregkh@...uxfoundation.org
Subject: Re: [PATCH 0/3] remap: Some fixes for bulk read/write callbacks in regmap_config support

On Thu, 16 Jun 2022 09:34:32 +0200, Javier Martinez Canillas wrote:
> This series contains fixes for a few issues found while testing the recent
> support for drivers to define bulk read/write callbacks in regmap_config.
> 
> I tested this with drivers/gpu/drm/solomon/ssd130x-spi.c, by converting it
> to use this new API instead of defining its own regmap bus for bulk write.
> 
> Patch #1 and patch #2 are fixes for regresions introduced by that commit
> and patch #3 adds regmap_config provided bulk write support to functions
> regmap_noinc_write() and regmap_bulk_write(), that were missed.
> 
> [...]

Applied to

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

Thanks!

[1/3] regmap: Re-introduce bulk read support check in regmap_bulk_read()
      commit: 5ac01e023a1b0492e159ad2f6734e0a350c1b6b6
[2/3] regmap: Make regmap_noinc_read() return -ENOTSUPP if map->read isn't set
      commit: f6e5c3850d1174bf3ca53457d64e6665f48c9041
[3/3] regmap: Wire up regmap_config provided bulk write in missed functions
      commit: 1db43c8ad90ce07311a3ef9af7ace758d79224f9

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