linux-kernel - Re: (subset) [PATCH v2 0/6] Migrate IDIO-16 GPIO drivers to regmap API

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: <167811175334.98202.15503041463855908266.b4-ty@kernel.org>
Date:   Mon, 06 Mar 2023 14:09:13 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linus.walleij@...aro.org, brgl@...ev.pl,
        William Breathitt Gray <william.gray@...aro.org>
Cc:     andriy.shevchenko@...ux.intel.com, linux-gpio@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v2 0/6] Migrate IDIO-16 GPIO drivers to regmap
 API

On Mon, 27 Feb 2023 11:45:21 -0500, William Breathitt Gray wrote:
> Changes in v2:
>  - Utilize memset32() to set status_buf for no_status case
>  - Utilize GENMASK() to generate status_buf mask
>  - Move no_status kernel doc line under runtime_pm line
>  - Add comma to end of idio_16_names initialization list
>  - Set io_port to true in idio_16_regmap_config
> 
> [...]

Applied to

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

Thanks!

[1/6] regmap-irq: Add no_status support
      commit: 4d60cac951fd2dfbf261b83abb805748abc8b995

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