linux-kernel - Re: [PATCH v3] spi: spi-imx: fix off-by-one in mx51 CPU mode burst length

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: <171084885691.22687.1626199972838540212.b4-ty@kernel.org>
Date: Tue, 19 Mar 2024 11:47:36 +0000
From: Mark Brown <broonie@...nel.org>
To: benjamin@...ler.one, carlos.song@....com, s.hauer@...gutronix.de, 
 shawnguo@...nel.org, stefanmoring@...il.com, 
 Adam Butcher <adam@...samine.co.uk>
Cc: kernel@...gutronix.de, linux-imx@....com, linux-kernel@...r.kernel.org, 
 linux-spi@...r.kernel.org
Subject: Re: [PATCH v3] spi: spi-imx: fix off-by-one in mx51 CPU mode burst
 length

On Mon, 18 Mar 2024 17:50:52 +0000, Adam Butcher wrote:
> c712c05e46c8 ("spi: imx: fix the burst length at DMA mode and CPU mode")
> corrects three cases of setting the ECSPI burst length but erroneously
> leaves the in-range CPU case one bit to big (in that field a value of
> 0 means 1 bit).  The effect was that transmissions that should have been
> 8-bit bytes appeared as 9-bit causing failed communication with SPI
> devices.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-imx: fix off-by-one in mx51 CPU mode burst length
      commit: cf6d79a0f5769b5f4d9579ddaf88d2c30b03b873

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