linux-kernel - Re: [PATCH] spi: atmel-quadspi: Factor out switching to Serial Memory Mode to function

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: <173454633792.186813.10395351752792939671.b4-ty@kernel.org>
Date: Wed, 18 Dec 2024 18:25:37 +0000
From: Mark Brown <broonie@...nel.org>
To: Varshini Rajendran <varshini.rajendran@...rochip.com>, 
 Tudor Ambarus <tudor.ambarus@...aro.org>, linux-spi@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 Bence Csókás <csokas.bence@...lan.hu>
Cc: Alexander Dahl <ada@...rsis.com>, 
 Nicolas Ferre <nicolas.ferre@...rochip.com>, 
 Alexandre Belloni <alexandre.belloni@...tlin.com>, 
 Claudiu Beznea <claudiu.beznea@...on.dev>
Subject: Re: [PATCH] spi: atmel-quadspi: Factor out switching to Serial
 Memory Mode to function

On Wed, 18 Dec 2024 16:17:54 +0100, Bence Csókás wrote:
> SAMA7G5 support (that was forward-ported from v6.1) re-introduced
> a bug that was fixed in v6.12, thankfully only in the codepath of
> the new SoC. But to prevent similar mistakes in the future, we
> split out the offending code to a function, and use this, fixed
> version everywhere.
> 
> To facilitate this, support function `atmel_qspi_update_config()`
> also had to be moved upwards. For best viewing experience, use
> `--color-moved-ws="allow-indentation-change" --color-moved`.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: atmel-quadspi: Factor out switching to Serial Memory Mode to function
      commit: f663898d047a7a0a04d30732b1405ee007fdd243

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