On Mon, 24 Apr 2023 15:55:46 +0530, Dhruva Gole wrote: > Using this macro makes the code more readable. > It also inits the members of dev_pm_ops in the following manner > without us explicitly needing to: > > .suspend = bcm63xx_spi_suspend, \ > .resume = bcm63xx_spi_resume, \ > .freeze = bcm63xx_spi_suspend, \ > .thaw = bcm63xx_spi_resume, \ > .poweroff = bcm63xx_spi_suspend, \ > .restore = bcm63xx_spi_resume > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: bcm63xx: use macro DEFINE_SIMPLE_DEV_PM_OPS commit: cc5f6fa4f6590e3b9eb8d34302ea43af4a3cfed7 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