linux-kernel - Re: [PATCH 1/2] dt-bindings: spi: fsl-lpspi: support i.MX95 LPSPI

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]

Date: Tue, 23 Jan 2024 12:32:05 +0000
From: Mark Brown <broonie@...nel.org>
To: conor+dt@...nel.org, robh+dt@...nel.org, 
 krzysztof.kozlowski+dt@...aro.org, han.xu@....com, haibo.chen@....com, 
 "Peng Fan (OSS)" <peng.fan@....nxp.com>
Cc: yogeshgaur.83@...il.com, linux-spi@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Peng Fan <peng.fan@....com>
Subject: Re: [PATCH 1/2] dt-bindings: spi: fsl-lpspi: support i.MX95 LPSPI

On Mon, 22 Jan 2024 17:15:09 +0800, Peng Fan (OSS) wrote:
> Add i.MX95 LPSPI compatible string, same as i.MX93 compatible with
> i.MX7ULP
> 
> 

Applied to

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

Thanks!

[1/2] dt-bindings: spi: fsl-lpspi: support i.MX95 LPSPI
      commit: 6685d552a0cc3a86e10dbe6d98e1b51717a27a63
[2/2] dt-bindings: spi: nxp-fspi: support i.MX93 and i.MX95
      commit: 18ab9e9e8889ecba23a5e8b7f8924f09284e33d8

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