linux-kernel - Re: [PATCH V2 0/1] regulator: da9121: add IRQ free to release function

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:   Wed, 02 Dec 2020 17:19:55 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Rob Herring <robh+dt@...nel.org>,
        Adam Ward <Adam.Ward.opensource@...semi.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
        Support Opensource <support.opensource@...semi.com>,
        Vincent Whitchurch <vincent.whitchurch@...s.com>,
        devicetree@...r.kernel.org
Subject: Re: [PATCH V2 0/1] regulator: da9121: add IRQ free to release function

On Wed, 2 Dec 2020 11:32:46 +0000, Adam Ward wrote:
> This patch fixes the DA9121 driver to disable the IRQ before cancelling
> the work, to be sure the IRQ doesn't restart it before all IRQs are
> masked
> 
> V2:
> 
>  - Fix to release IRQ if regmap error fails probe
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: da9121: Request IRQ directly and free in release function to avoid masking race
      commit: 5e191d2e05a4fe098632006bb3afa5e21c8789db

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