linux-kernel - Re: [PATCH v2 0/4] regmap-irq: Cleanups and remove unused functionality

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <168386589016.356341.17261279641586360743.b4-ty@kernel.org>
Date:   Fri, 12 May 2023 13:31:30 +0900
From:   Mark Brown <broonie@...nel.org>
To:     Aidan MacDonald <aidanmacdonald.0x0@...il.com>
Cc:     gregkh@...uxfoundation.org, rafael@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/4] regmap-irq: Cleanups and remove unused
 functionality

On Thu, 11 May 2023 10:13:38 +0100, Aidan MacDonald wrote:
> v1->v2:
> Rebase patches against for-6.5 branch of broonie/regmap.git.
> 
> - 1/4 and 2/4 remove unused, deprecated functionality
> - 3/4 makes the behavior of .handle_mask_sync() a bit more consistent
>   w.r.t. mask and unmask registers, to aid maintainability.
> - 4/4 removes now-unused "inverted mask/unmask" compatibility code.
> 
> [...]

Applied to

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

Thanks!

[1/4] regmap-irq: Remove type registers
      commit: f05cbadce7e409b38acdf21f0a05d4420afa1b11
[2/4] regmap-irq: Remove support for not_fixed_stride
      commit: 72cc0f523babca3886421721aa662c7d352a6d32
[3/4] regmap-irq: Minor adjustments to .handle_mask_sync()
      commit: a240d23ee9dce2a9fe68d614f19a463d7029fb87
[4/4] regmap-irq: Drop backward compatibility for inverted mask/unmask
      commit: 0a3a56875500aaa5b0bc8f857ed46c8cd46d0775

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