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

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 for Android: free password hash cracker in your pocket

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

Message-Id: <167659885855.51558.18015897607199701976.b4-ty@kernel.org>
Date:   Fri, 17 Feb 2023 01:54:18 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH] spi: spidev: drop the incorrect notice from Kconfig

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