Skip to contentSkip to conversation

spi: spidev: drop the incorrect notice from Kconfig

PATCH In review Bartosz Golaszewski 2 participants 2 messages Feb 16, 2023 – Feb 17, 2023 SPI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi: spidev: drop the incorrect notice from Kconfig

From: Bartosz Golaszewski <[email protected]>

The spidev interface has been de-facto stable for many years. This notice has been unchanged since 2007 and is incorrect so remove it.

---
 drivers/spi/Kconfig | 3 ---
 1 file changed, 3 deletions(-)
drivers/spi/Kconfig +0 -3
index 3b1c0878bb85..2a2ac3aa13c9 100644
@@ -1166,9 +1166,6 @@ config SPI_SPIDEV
 	help
 	  This supports user mode SPI protocol drivers.
 
-	  Note that this application programming interface is EXPERIMENTAL
-	  and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
-
 config SPI_LOOPBACK_TEST
 	tristate "spi loopback test framework support"
 	depends on m
Signature · 1 line
2.37.2
maintainer
#1 lore raw
Quoted 4 lines · Bartosz Golaszewski

The spidev interface has been de-facto stable for many years. This notice has been unchanged since 2007 and is incorrect so remove it.

Applied to

broonie/spi.git for-next

Thanks!

[1/1] spi: spidev: drop the incorrect notice from Kconfig

      commit: a46ce4f884817c66d0dc303b663b53b37d2baa24

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