linux-kernel - Re: [PATCH v2 0/7] spi: multi CS cleanup and controller CS limit removal

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: <175862672270.1039628.11616279717463508641.b4-ty@kernel.org>
Date: Tue, 23 Sep 2025 13:25:22 +0200
From: Mark Brown <broonie@...nel.org>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>, 
 Jonas Gorski <jonas.gorski@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Marc Kleine-Budde <mkl@...gutronix.de>
Subject: Re: [PATCH v2 0/7] spi: multi CS cleanup and controller CS limit
 removal

On Mon, 15 Sep 2025 20:37:18 +0200, Jonas Gorski wrote:
> This series aims at cleaning up the current multi CS parts and removing
> the CS limit per controller that was introduced with the multi CS
> support.
> 
> To do this, store the assigned chip selects per device in
> spi_device::num_chipselects, which allows us to use that instead of
> SPI_CS_CNT_MAX for most loops, as well as remove the check for
> SPI_INVALID_CS for any chip select.
> 
> [...]

Applied to

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

Thanks!

[1/7] spi: fix return code when spi device has too many chipselects
      commit: 188f63235bcdd207646773a8739387d85347ed76
[2/7] spi: keep track of number of chipselects in spi_device
      commit: 099f942182e3695554cba44e4bafb08a4111b50f
[3/7] spi: move unused device CS initialization to __spi_add_device()
      commit: 1c923f624439b26b6740cdd2a9f7a12b1968f3f3
[4/7] spi: drop check for validity of device chip selects
      commit: f3982daccf42cefcd80218c76a6b5dd134fe97e3
[5/7] spi: don't check spi_controller::num_chipselect when parsing a dt device
      commit: 83c522fb642384aef43697aa5c7686363e9e92dd
[6/7] spi: reduce device chip select limit again
      commit: 08fda410bae41cc8dde9697f9104da525be53153
[7/7] spi: rename SPI_CS_CNT_MAX => SPI_DEVICE_CS_CNT_MAX
      commit: e336ab509b43ea601801dfa05b4270023c3ed007

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