linux-kernel - Re: [PATCH] spi: dt-bindings: spi-mux: Drop "spi-max-frequency" as required

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: <175266090631.17966.7228159355506888801.b4-ty@kernel.org>
Date: Wed, 16 Jul 2025 11:15:06 +0100
From: Mark Brown <broonie@...nel.org>
To: Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Chris Packham <chris.packham@...iedtelesis.co.nz>, 
 "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: spi-mux: Drop "spi-max-frequency" as
 required

On Tue, 15 Jul 2025 15:27:10 -0500, Rob Herring (Arm) wrote:
> There's little reason to require the SPI mux to define a maximum bus
> frequency as the muxing is just the chip select and devices still define
> their maximum freq. In fact, several users don't set "spi-max-frequency"
> which caused warnings.
> 
> 

Applied to

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

Thanks!

[1/1] spi: dt-bindings: spi-mux: Drop "spi-max-frequency" as required
      commit: d5255ae7ec48ac1f702e95b472801dbb7bf1e97f

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