linux-kernel - Re: [PATCH] spi: spi-fsl-lpspi: limit PRESCALE bit in TCR register

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: <172416045279.160388.12340685060459162773.b4-ty@kernel.org>
Date: Tue, 20 Aug 2024 14:27:32 +0100
From: Mark Brown <broonie@...nel.org>
To: carlos.song@....com
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 imx@...ts.linux.dev
Subject: Re: [PATCH] spi: spi-fsl-lpspi: limit PRESCALE bit in TCR register

On Tue, 20 Aug 2024 15:06:58 +0800, carlos.song@....com wrote:
> Referring to the errata ERR051608 of I.MX93, LPSPI TCR[PRESCALE]
> can only be configured to be 0 or 1, other values are not valid
> and will cause LPSPI to not work.
> 
> Add the prescale limitation for LPSPI in I.MX93. Other platforms
> are not affected.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-fsl-lpspi: limit PRESCALE bit in TCR register
      commit: 783bf5d09f86b9736605f3e01a3472e55ef98ff8

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