linux-kernel - Re: (subset) [PATCH 0/3] spi: OCTAL mode fixes

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: <171874084769.162949.15399594588029522021.b4-ty@kernel.org>
Date: Tue, 18 Jun 2024 21:00:47 +0100
From: Mark Brown <broonie@...nel.org>
To: patrice.chotard@...s.st.com
Cc: linux-spi@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 christophe.kerello@...s.st.com
Subject: Re: (subset) [PATCH 0/3] spi: OCTAL mode fixes

On Tue, 18 Jun 2024 15:29:48 +0200, patrice.chotard@...s.st.com wrote:
> During tests performed using spidev_test in OCTAL mode with spi-stm32-qspi.c,
> several issues has been found :
>   _ OCTAL mode wasn't supported in spi.c
>   _ CCR register wasn't set correctly when OCTAL mode is set in spi-stm32-qspi.c.
>   _ Fix dual flash mode sanity test in spi-stm32-qspi.c
> 
> Patrice Chotard (3):
>   spi: stm32: qspi: Fix dual flash mode sanity test in
>     stm32_qspi_setup()
>   spi: stm32: qspi: Clamp stm32_qspi_get_mode() output to CCR_BUSWIDTH_4
>   spi: add OCTAL mode support
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: stm32: qspi: Fix dual flash mode sanity test in stm32_qspi_setup()
      commit: c2bd0791c5f02e964402624dfff45ca8995f5397
[2/3] spi: stm32: qspi: Clamp stm32_qspi_get_mode() output to CCR_BUSWIDTH_4
      commit: 63deee52811b2f84ed2da55ad47252f0e8145d62
[3/3] spi: add OCTAL mode support
      commit: d6a711a898672dd873aab3844f754a3ca40723a5

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