[PATCH 0/3] spi: axiado: spi: axiado: fix runtime pm imbalance on probe failure

Johan Hovold posted 3 patches 1 month, 3 weeks ago
drivers/spi/spi-axiado.c | 31 +++++++++++++++++++------------
1 file changed, 19 insertions(+), 12 deletions(-)
[PATCH 0/3] spi: axiado: spi: axiado: fix runtime pm imbalance on probe failure
Posted by Johan Hovold 1 month, 3 weeks ago
The series fixes some runtime PM related issues in the axiado driver.

Included is also a couple of related cleanups.

Johan


Johan Hovold (3):
  spi: axiado: fix runtime pm imbalance on probe failure
  spi: axiado: rename probe error labels
  spi: axiado: clean up probe return value

 drivers/spi/spi-axiado.c | 31 +++++++++++++++++++------------
 1 file changed, 19 insertions(+), 12 deletions(-)

-- 
2.52.0
Re: [PATCH 0/3] spi: axiado: spi: axiado: fix runtime pm imbalance on probe failure
Posted by Mark Brown 1 month, 3 weeks ago
On Tue, 21 Apr 2026 16:39:22 +0200, Johan Hovold wrote:
> spi: axiado: spi: axiado: fix runtime pm imbalance on probe failure
> 
> The series fixes some runtime PM related issues in the axiado driver.
> 
> Included is also a couple of related cleanups.
> 
> Johan
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: axiado: fix runtime pm imbalance on probe failure
      https://git.kernel.org/broonie/spi/c/cde1a784e4d5
[2/3] spi: axiado: rename probe error labels
      https://git.kernel.org/broonie/spi/c/821f0951b208
[3/3] spi: axiado: clean up probe return value
      https://git.kernel.org/broonie/spi/c/2b20e6742442

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