linux-kernel - Re: [PATCH v2] spi: dt-bindings: nuvoton,npcm-pspi: Convert to DT schema

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: <176296976083.48834.13469679974248275009.b4-ty@kernel.org>
Date: Wed, 12 Nov 2025 17:49:20 +0000
From: Mark Brown <broonie@...nel.org>
To: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, 
 avifishman70@...il.com, tali.perry1@...il.com, joel@....id.au, 
 venture@...gle.com, yuenn@...gle.com, benjaminfair@...gle.com, 
 andrew@...econstruct.com.au, Tomer Maimon <tmaimon77@...il.com>
Cc: openbmc@...ts.ozlabs.org, devicetree@...r.kernel.org, 
 linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] spi: dt-bindings: nuvoton,npcm-pspi: Convert to DT
 schema

On Wed, 12 Nov 2025 17:09:50 +0200, Tomer Maimon wrote:
> Convert the Nuvoton NPCM PSPI binding to DT schema format.
> 
> Also update the binding to fix shortcoming:
>  * Drop clock-frequency property: it is never read in the NPCM PSPI
>    driver and has no effect.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: dt-bindings: nuvoton,npcm-pspi: Convert to DT schema
      commit: 1d562ba0aa7df81335bf96c02be77efe8d5bab87

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