linux-kernel - Re: [PATCH] spi: cadence-qspi: Remove redundant pm_runtime_mark_last

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: <176580716842.161463.10027388090640755995.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:59:28 +0900
From: Mark Brown <broonie@...nel.org>
To: Akif Ejaz <akifejaz40@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 alitariq45892@...il.com
Subject: Re: [PATCH] spi: cadence-qspi: Remove redundant
 pm_runtime_mark_last_busy call

On Wed, 03 Dec 2025 23:19:21 +0500, Akif Ejaz wrote:
> The pm_runtime_mark_last_busy() call is redundant in probe function
> as pm_runtime_put_autosuspend() already calls pm_runtime_mark_last_busy()
> internally to update the last access time of the device before queuing
> autosuspend.
> 
> Remove the pm_runtime_mark_last_busy() call from the probe function.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: cadence-qspi: Remove redundant pm_runtime_mark_last_busy call
      commit: 28d21dfcea0121afec04451733a6c553fd319c8e

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