[PATCH] spi: spidev: drop the incorrect notice from Kconfig

[PATCH] spi: spidev: drop the incorrect notice from Kconfig

[Bartosz Golaszewski]

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

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

Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
 drivers/spi/Kconfig | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 3b1c0878bb85..2a2ac3aa13c9 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -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
-- 
2.37.2

Re: [PATCH] spi: spidev: drop the incorrect notice from Kconfig

[Mark Brown]

On Thu, 16 Feb 2023 13:30:14 +0100, Bartosz Golaszewski wrote:
> 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