linux-kernel - Re: [PATCH 0/2] spi: rpc-if: Add resume support for RZ/G3E

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: <175862672007.1039628.355731344831251638.b4-ty@kernel.org>
Date: Tue, 23 Sep 2025 13:25:20 +0200
From: Mark Brown <broonie@...nel.org>
To: Biju Das <biju.das.jz@...renesas.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Geert Uytterhoeven <geert+renesas@...der.be>, 
 Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@...renesas.com>, 
 Biju Das <biju.das.au@...il.com>, linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH 0/2] spi: rpc-if: Add resume support for RZ/G3E

On Sun, 21 Sep 2025 12:26:44 +0100, Biju Das wrote:
> On RZ/G3E using PSCI, s2ram powers down the SoC. After resume,
> reinitialize the hardware for SPI operations.
> 
> Also Replace the macro SIMPLE_DEV_PM_OPS->DEFINE_SIMPLE_DEV_PM_OPS macro
> and use pm_sleep_ptr(). This lets us drop the check for CONFIG_PM_SLEEP
> and __maybe_unused attribute from PM functions.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: rpc-if: Drop deprecated SIMPLE_DEV_PM_OPS
      commit: 81ef2022b311c7c4f29011f778442635acfaba90
[2/2] spi: rpc-if: Add resume support for RZ/G3E
      commit: 2bfb20b65d9bc1d0de58f8c28ca9d6f1d27bbc01

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