linux-kernel - Re: [PATCH] spi: spi-fsl-lpspi: remove redundant spi_controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <171215116351.907765.4790730663496497496.b4-ty@kernel.org>
Date: Wed, 03 Apr 2024 14:32:43 +0100
From: Mark Brown <broonie@...nel.org>
To: alexander.sverdlin@...mens.com, carlos.song@....com
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 imx@...ts.linux.dev, haibo.chen@....com, jun.li@....com, linux-imx@....com
Subject: Re: [PATCH] spi: spi-fsl-lpspi: remove redundant
 spi_controller_put call

On Wed, 03 Apr 2024 16:40:29 +0800, carlos.song@....com wrote:
> devm_spi_alloc_controller will allocate an SPI controller and
> automatically release a reference on it when dev is unbound from
> its driver. It doesn't need to call spi_controller_put explicitly
> to put the reference when lpspi driver failed initialization.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-fsl-lpspi: remove redundant spi_controller_put call
      commit: bff892acf79cec531da6cb21c50980a584ce1476

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