linux-kernel - Re: [PATCH v2 0/2] use read_poll

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: <158739405971.23005.4028325729913635797.b4-ty@kernel.org>
Date:   Mon, 20 Apr 2020 15:47:39 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Dejin Zheng <zhengdejin5@...il.com>
Cc:     linux-kernel@...r.kernel.org, Markus.Elfring@....de
Subject: Re: [PATCH v2 0/2] use read_poll_timeout macro to simplify code

On Mon, 20 Apr 2020 21:46:45 +0800, Dejin Zheng wrote:
> Simplify implementation of regmap_read_poll_timeout() macro and
> regmap_field_read_poll_timeout by read_poll_timeout() macro, they have
> many similar codes.
> 
> v1 -> v2:
> 	- modify the commit comments by Markus's suggestion .
> 
> [...]

Applied to

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

Thanks!

[1/2] regmap: Simplify implementation of the regmap_read_poll_timeout() macro
      commit: e44ab4e14d6f4c448ae555132090c1a116b19e5c
[2/2] regmap: Simplify implementation of the regmap_field_read_poll_timeout() macro
      commit: 148c01d176237115d9c2805f6d29c0b6a72fbd10

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