mbox series

[0/2] spi: qup: Convert to platform remove callback returning void

Message ID 20230330210341.2459548-1-u.kleine-koenig@pengutronix.de (mailing list archive)
Headers show
Series spi: qup: Convert to platform remove callback returning void | expand

Message

Uwe Kleine-König March 30, 2023, 9:03 p.m. UTC
Hello,

after fixing the error handling in the .remove() callback of the qup
driver, convert it to .remove_new() preparing to make platform driver's
remove functions return void.

Best regards
Uwe

Uwe Kleine-König (2):
  spi: qup: Don't skip cleanup in remove's error path
  spi: qup: Convert to platform remove callback returning void

 drivers/spi/spi-qup.c | 28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)

base-commit: fe15c26ee26efa11741a7b632e9f23b01aca4cc6

Comments

Mark Brown April 4, 2023, 3:41 p.m. UTC | #1
On Thu, 30 Mar 2023 23:03:39 +0200, Uwe Kleine-König wrote:
> after fixing the error handling in the .remove() callback of the qup
> driver, convert it to .remove_new() preparing to make platform driver's
> remove functions return void.
> 
> Best regards
> Uwe
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: qup: Don't skip cleanup in remove's error path
      commit: 61f49171a43ab1f80c73c5c88c508770c461e0f2
[2/2] spi: qup.c: Convert to platform remove callback returning void
      commit: dea8e70f68f4105279bbc6de4d68d89fb07665c2

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