linux-kernel - Re: [PATCH v3] regmap: irq: Add support to clear ack registers

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, 05 Oct 2020 18:54:17 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Laxminath Kasam <lkasam@...eaurora.org>,
        linux-kernel@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     srinivas.kandagatla@...aro.org
Subject: Re: [PATCH v3] regmap: irq: Add support to clear ack registers

On Mon, 5 Oct 2020 19:47:19 +0530, Laxminath Kasam wrote:
> For particular codec HWs have requirement to toggle interrupt clear
> register twice 0->1->0. To accommodate it, need to add one more field
> (clear_ack) in the regmap_irq struct and update regmap-irq driver to
> support it.

Applied to

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

Thanks!

[1/1] regmap: irq: Add support to clear ack registers
      commit: 3a6f0fb7b8eb5ef0447da1332225b8c87ee207d0

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