linux-kernel - Re: [PATCH resubmit2] spi: atmel-quadspi: remove references to runtime PM on error path

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: <173979506523.23527.7426002054333724142.b4-ty@kernel.org>
Date: Mon, 17 Feb 2025 12:24:25 +0000
From: Mark Brown <broonie@...nel.org>
To: Varshini Rajendran <varshini.rajendran@...rochip.com>, 
 Tudor Ambarus <tudor.ambarus@...aro.org>, linux-spi@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 Bence Csókás <csokas.bence@...lan.hu>
Cc: Claudiu Beznea <claudiu.beznea@...on.dev>, 
 Durai Manickam KR <durai.manickamkr@...rochip.com>, 
 Alexander Dahl <ada@...rsis.com>, 
 Nicolas Ferre <nicolas.ferre@...rochip.com>, 
 Alexandre Belloni <alexandre.belloni@...tlin.com>
Subject: Re: [PATCH resubmit2] spi: atmel-quadspi: remove references to
 runtime PM on error path

On Fri, 07 Feb 2025 13:21:45 +0100, Bence Csókás wrote:
> There is no need to call runtime PM put APIs on error path of
> `atmel_qspi_sama7g5_transfer()` as the caller (`atmel_qspi_exec_op()`)
> of it will take care of this if needed.
> 
> 

Applied to

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

Thanks!

[1/1] spi: atmel-quadspi: remove references to runtime PM on error path
      commit: 99e6ea912340d6a262a60d5dd0c87c5e7b2d6ff2

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