linux-kernel - Re: [PATCH] spi: imx: remove CLK calculation and check for target mode

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: <176247326802.2483158.5597170860062557920.b4-ty@kernel.org>
Date: Thu, 06 Nov 2025 23:54:28 +0000
From: Mark Brown <broonie@...nel.org>
To: frank.li@....com, shawnguo@...nel.org, s.hauer@...gutronix.de, 
 kernel@...gutronix.de, festevam@...il.com, carlos.song@....com
Cc: linux-spi@...r.kernel.org, imx@...ts.linux.dev, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: imx: remove CLK calculation and check for target
 mode

On Fri, 24 Oct 2025 13:52:11 +0800, carlos.song@....com wrote:
> In target mode, the clock signal is controlled by the master. Target does
> not need to check, calculate and configure the clock frequency division.
> The target can directly use the root clock to sample the SCL signal.
> 
> Therefore, remove check, calculation and frequency division function of
> the clock for target mode.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: imx: remove CLK calculation and check for target mode
      commit: 55d03b5b5bdd04daf9a35ce49db18d8bb488dffb

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