linux-kernel - Re: [PATCH] dt-bindings: spi-mux: Add reference to spi-peripheral-props.yaml 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]

Date:   Thu, 06 Jan 2022 20:28:31 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Chris Packham <chris.packham@...iedtelesis.co.nz>,
        Rob Herring <robh@...nel.org>
Cc:     linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: spi-mux: Add reference to spi-peripheral-props.yaml schema

On Wed, 5 Jan 2022 12:32:33 -0600, Rob Herring wrote:
> The spi-mux serves as both a SPI peripheral and controller, so add a
> reference to spi-peripheral-props.yaml in addition to
> spi-controller.yaml. This is necessary to avoid unevaluatedProperties
> warnings once those are fully enabled.
> 
> 

Applied to

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

Thanks!

[1/1] dt-bindings: spi-mux: Add reference to spi-peripheral-props.yaml schema
      commit: 709c81b55c6aa74a6cdad27bdc224f50962b6ad9

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