On Tue, 16 Jun 2020 13:30:35 +0200, patrice.chotard@xxxxxx wrote: > In case of -EPROBE_DEFER, stm32_qspi_release() was called > in any case which unregistered driver from pm_runtime framework > even if it has not been registered yet to it. This leads to: > > stm32-qspi 58003000.spi: can't setup spi0.0, status -13 > spi_master spi0: spi_device register error /soc/spi@58003000/mx66l51235l@0 > spi_master spi0: Failed to create SPI device for /soc/spi@58003000/mx66l51235l@0 > stm32-qspi 58003000.spi: can't setup spi0.1, status -13 > spi_master spi0: spi_device register error /soc/spi@58003000/mx66l51235l@1 > spi_master spi0: Failed to create SPI device for /soc/spi@58003000/mx66l51235l@1 > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: stm32-qspi: Fix error path in case of -EPROBE_DEFER commit: 35700e221b18fa53401e5f315be90af9e0bbcdca 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