linux-kernel - Re: [PATCH v1 1/2] regmap-irq: Remove unused type

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: <167660010179.68139.12889888972386660880.b4-ty@kernel.org>
Date:   Fri, 17 Feb 2023 02:15:01 +0000
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 v1 1/2] regmap-irq: Remove unused type_invert flag

On Thu, 16 Feb 2023 22:31:59 +0000, Aidan MacDonald wrote:
> type_invert is deprecated and no longer used; it can now be removed.
> 
> 

Applied to

   broonie/regmap.git for-next

Thanks!

[1/2] regmap-irq: Remove unused type_invert flag
      commit: 483e6ea1b35aaeffd9b6e6e660d756be49c2a9f5
[2/2] regmap-irq: Remove unused mask_invert flag
      commit: c74e7af1245b2073930afc9a2a340d91e08f0f14

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