linux-kernel - Re: [PATCH] spi: stm32: fix accidential revert to byte-sized transfer splitting

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: <169265215965.467713.8072981996743958072.b4-ty@kernel.org>
Date:   Mon, 21 Aug 2023 22:09:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     valentin.caron@...s.st.com,
        Alain Volmat <alain.volmat@...s.st.com>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>,
        Leonard Göhrs <l.goehrs@...gutronix.de>
Cc:     conor+dt@...nel.org, devicetree@...r.kernel.org,
        krzysztof.kozlowski+dt@...aro.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com, robh+dt@...nel.org
Subject: Re: [PATCH] spi: stm32: fix accidential revert to byte-sized
 transfer splitting

On Wed, 16 Aug 2023 16:52:37 +0200, Leonard Göhrs wrote:
> Commit 6f486556abe35 ("spi: stm32: renaming of spi_master into
> spi_controller") included an accidential reverted of a change added in
> commit 1e4929112507f ("spi: stm32: split large transfers based on word
> size instead of bytes").
> 
> This breaks large SPI transfers with word sizes > 8 bits, which are
> e.g. common when driving MIPI DBI displays.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: stm32: fix accidential revert to byte-sized transfer splitting
      commit: 715dc9a1f0c8ae0bbd4e5b37f9a165ea39e47fe9

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