linux-kernel - Re: [PATCH v1] dt-bindings: spi: samsung: add exynosautov920-spi compatible

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: <174790605339.30110.2721459135664956247.b4-ty@kernel.org>
Date: Thu, 22 May 2025 10:27:33 +0100
From: Mark Brown <broonie@...nel.org>
To: andi.shyti@...nel.org, tudor.ambarus@...aro.org, robh@...nel.org, 
 krzk+dt@...nel.org, conor+dt@...nel.org, Faraz Ata <faraz.ata@...sung.com>
Cc: linux-spi@...r.kernel.org, linux-samsung-soc@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 alim.akhtar@...sung.com, rosa.pila@...sung.com, dev.tailor@...sung.com
Subject: Re: [PATCH v1] dt-bindings: spi: samsung: add exynosautov920-spi
 compatible

On Wed, 21 May 2025 14:13:24 +0530, Faraz Ata wrote:
> Add "samsung,exynosautov920-spi" dedicated compatible for
> SPI found in ExynosAutov920 SoC.
> 
> 

Applied to

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

Thanks!

[1/1] dt-bindings: spi: samsung: add exynosautov920-spi compatible
      commit: 477d16c0919e82a7f5f673a6e3ae39a17c773037

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