linux-kernel - Re: [PATCH] drivers: spi: cadence-quadspi: Handle spi_unregister

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: <165237311899.1053498.14444513819547781414.b4-ty@kernel.org>
Date:   Thu, 12 May 2022 17:31:58 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, vaishnav.a@...com,
        linux-kernel@...r.kernel.org
Cc:     vigneshr@...com, j-keerthy@...com, p.yadav@...com
Subject: Re: [PATCH] drivers: spi: cadence-quadspi: Handle spi_unregister_master() in remove()

On Wed, 11 May 2022 17:25:16 +0530, Vaishnav Achath wrote:
> Currently devres managed removal of the spi_controller happens after
> removing the power domain of the host platform_device.While this
> does not affect the clean removal of the controller, but affects
> graceful removal of the child devices if the child  device removal
> requires issuing commands over SPI.
> 
> Eg. flash device being soft reset to 1S-1S-1S mode before removal
> so that on next probe operations in 1S-1S-1S mode is successful.
> 
> [...]

Applied to

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

Thanks!

[1/1] drivers: spi: cadence-quadspi: Handle spi_unregister_master() in remove()
      commit: 606e5d408184989f53028125e0cb5aa6713362d5

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