[PATCH 0/5] spi: controller registration fixes

Johan Hovold posted 5 patches 3 weeks, 4 days ago
drivers/spi/spi.c | 60 +++++++++++++++++++++++------------------------
1 file changed, 29 insertions(+), 31 deletions(-)
[PATCH 0/5] spi: controller registration fixes
Posted by Johan Hovold 3 weeks, 4 days ago
This series fixes a few issues related to controller registration found
through inspection.

Johan


Johan Hovold (5):
  spi: fix use-after-free on controller registration failure
  spi: fix statistics allocation
  spi: drop unused devres statistics allocation
  spi: fix misleading controller registration kernel-doc
  spi: fix misleading controller deregistration kernel-doc

 drivers/spi/spi.c | 60 +++++++++++++++++++++++------------------------
 1 file changed, 29 insertions(+), 31 deletions(-)

-- 
2.52.0
Re: [PATCH 0/5] spi: controller registration fixes
Posted by Mark Brown 3 weeks ago
On Thu, 12 Mar 2026 16:18:12 +0100, Johan Hovold wrote:
> This series fixes a few issues related to controller registration found
> through inspection.
> 
> Johan
> 
> 
> Johan Hovold (5):
>   spi: fix use-after-free on controller registration failure
>   spi: fix statistics allocation
>   spi: drop unused devres statistics allocation
>   spi: fix misleading controller registration kernel-doc
>   spi: fix misleading controller deregistration kernel-doc
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: fix use-after-free on controller registration failure
      https://git.kernel.org/broonie/misc/c/8634e05b08ea
[2/5] spi: fix statistics allocation
      https://git.kernel.org/broonie/misc/c/dee0774bbb2a
[3/5] spi: drop unused devres statistics allocation
      https://git.kernel.org/broonie/misc/c/d5b4cb41b9a2
[4/5] spi: fix misleading controller registration kernel-doc
      https://git.kernel.org/broonie/misc/c/edc463d72d69
[5/5] spi: fix misleading controller deregistration kernel-doc
      https://git.kernel.org/broonie/misc/c/3f174274d224

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
Re: [PATCH 0/5] spi: controller registration fixes
Posted by Mark Brown 3 weeks ago
On Thu, 12 Mar 2026 16:18:12 +0100, Johan Hovold wrote:
> spi: controller registration fixes
> 
> This series fixes a few issues related to controller registration found
> through inspection.
> 
> Johan
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: fix use-after-free on controller registration failure
      https://git.kernel.org/broonie/spi/c/8634e05b08ea
[2/5] spi: fix statistics allocation
      https://git.kernel.org/broonie/spi/c/dee0774bbb2a
[3/5] spi: drop unused devres statistics allocation
      https://git.kernel.org/broonie/spi/c/d5b4cb41b9a2
[4/5] spi: fix misleading controller registration kernel-doc
      https://git.kernel.org/broonie/spi/c/edc463d72d69
[5/5] spi: fix misleading controller deregistration kernel-doc
      https://git.kernel.org/broonie/spi/c/3f174274d224

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