linux-kernel - Re: [PATCH 1/2] regmap: regmap-irq: Move handle_post_irq to before pm_runtime

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:   Thu, 01 Jun 2023 14:40:45 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Charles Keepax <ckeepax@...nsource.cirrus.com>
Cc:     gregkh@...uxfoundation.org, rafael@...nel.org,
        patches@...nsource.cirrus.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] regmap: regmap-irq: Move handle_post_irq to before
 pm_runtime_put

On Thu, 01 Jun 2023 11:10:35 +0100, Charles Keepax wrote:
> Typically handle_post_irq is going to be used to manage some
> additional chip specific hardware operations required on each IRQ,
> these are very likely to want the chip to be resumed. For example the
> current in tree user max77620 uses this to toggle a global mask bit,
> which would obviously want the device resumed. It is worth noting this
> device does not specify the runtime_pm flag in regmap_irq_chip, so
> there is no actual issue.
> 
> [...]

Applied to

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

Thanks!

[1/2] regmap: regmap-irq: Move handle_post_irq to before pm_runtime_put
      commit: 02534c8e967b51940ae7c0cd99befe216f1c2c8d
[2/2] regmap: Add missing cache_only checks
      commit: 99e8dd39f34333d745e6c220be5d166e85214e6c

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