linux-kernel - Re: [PATCH 1/1] spi: Fix SPI slave probe failure

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: <171880243095.125187.8391249561773435131.b4-ty@kernel.org>
Date: Wed, 19 Jun 2024 14:07:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, git@....com, 
 amitrkcian2002@...il.com
Subject: Re: [PATCH 1/1] spi: Fix SPI slave probe failure

On Mon, 17 Jun 2024 21:00:52 +0530, Amit Kumar Mahapatra wrote:
> While adding a SPI device, the SPI core ensures that multiple logical CS
> doesn't map to the same physical CS. For example, spi->chip_select[0] !=
> spi->chip_select[1] and so forth. However, unlike the SPI master, the SPI
> slave doesn't have the list of chip selects, this leads to probe failure
> when the SPI controller is configured as slave. Update the
> __spi_add_device() function to perform this check only if the SPI
> controller is configured as master.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: Fix SPI slave probe failure
      commit: 2c1b7bbe253986619fa5623a13055316e730e746

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