linux-kernel - Re: [PATCH v2 0/2] spi: spi-stm32-ospi: dt-bindings 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174413059164.2217856.1996505992127496471.b4-ty@kernel.org>
Date: Tue, 08 Apr 2025 17:43:11 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Maxime Coquelin <mcoquelin.stm32@...il.com>, 
 Alexandre Torgue <alexandre.torgue@...s.st.com>, 
 Philipp Zabel <p.zabel@...gutronix.de>, 
 Patrice Chotard <patrice.chotard@...s.st.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
 christophe.kerello@...s.st.com, linux-spi@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] spi: spi-stm32-ospi: dt-bindings fixes

On Mon, 24 Mar 2025 10:40:12 +0100, Patrice Chotard wrote:
> Make "resets" property mandatory.
> Update spi-stm32-ospi driver and dt-bindings accordingly.
> 
> 

Applied to

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

Thanks!

[1/2] spi: dt-bindings: st,stm32mp25-ospi: Make "resets" a required property
      commit: d58b4eb7c03cabb10d4eebc89d7596e06376e54d
[2/2] spi: spi-stm32-ospi: Make "resets" a required property
      commit: 69e3433fa5e24edc94e94b4f34e3dbb754bdedbf

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