linux-kernel - Re: [RFT PATCH] spi: stm32: ignore Rx queue not empty in stm32f4 Tx only 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: <164554395470.3556326.18373522553071948963.b4-ty@kernel.org>
Date:   Tue, 22 Feb 2022 15:32:34 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Ahmad Fatoum <a.fatoum@...gutronix.de>,
        Alain Volmat <alain.volmat@...s.st.com>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>
Cc:     kernel@...gutronix.de, linux-arm-kernel@...ts.infradead.org,
        Dillon Min <dillon.minfei@...il.com>,
        linux-spi@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-kernel@...r.kernel.org
Subject: Re: [RFT PATCH] spi: stm32: ignore Rx queue not empty in stm32f4 Tx only mode

On Tue, 1 Feb 2022 12:51:41 +0100, Ahmad Fatoum wrote:
> STM32F4_SPI_SR_RXNE and STM32F4_SPI_SR_OVR are distinct bits in the same
> status register.  ~STM32F4_SPI_SR_OVR | STM32F4_SPI_SR_RXNE is thus
> equal to ~STM32F4_SPI_SR_OVR.
> 
> The original intention was likely for transmission-only transfers to
> ignore interrupts both for when the Rx queue has bytes (RXNE) as well
> as when these bytes haven't been read in time (OVR).
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: stm32: ignore Rx queue not empty in stm32f4 Tx only mode
      commit: 5741150c808b2bbeb1017609f3029daf6651b7d5

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