linux-kernel - Re: [PATCH] spi: dt-bindings: snps,dw-abp-ssi: Allow up to 16 chip-selects

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: <176604340821.24947.4105982029008973557.b4-ty@kernel.org>
Date: Thu, 18 Dec 2025 07:36:48 +0000
From: Mark Brown <broonie@...nel.org>
To: Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, "Rob Herring (Arm)" <robh@...nel.org>
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: dt-bindings: snps,dw-abp-ssi: Allow up to 16
 chip-selects

On Mon, 15 Dec 2025 17:03:22 -0600, Rob Herring (Arm) wrote:
> At least the Microchip Sparx5 supports up to 16 chip-selects, so
> increase the maximum. The pattern for the child unit-address was
> unconstrained, so update it to match the maximum number of
> chip-selects.
> 
> 

Applied to

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

Thanks!

[1/1] spi: dt-bindings: snps,dw-abp-ssi: Allow up to 16 chip-selects
      commit: 1d24636a9c87c32ec626a56593c98544e6c49fef

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