linux-kernel - Re: [PATCH] spi: dt-bindings: mediatek: Set min size for 'mediatek,pad-select'

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: <164624047624.1145410.7673106466966850861.b4-ty@kernel.org>
Date:   Wed, 02 Mar 2022 17:01:16 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Matthias Brugger <matthias.bgg@...il.com>,
        Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
        Leilk Liu <leilk.liu@...iatek.com>
Cc:     linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
        devicetree@...r.kernel.org, linux-spi@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] spi: dt-bindings: mediatek: Set min size for 'mediatek,pad-select'

On Tue, 1 Mar 2022 15:23:57 -0600, Rob Herring wrote:
> The minimum array length defaults to the same size as the maximum. For
> 'mediatek,pad-select', the example has a length of 2 and in-tree .dts
> files have a length of 1, but the schema says the length must be 4.
> 
> There's currently no warning in the example because the schema fixups
> are not handling this case correctly.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: dt-bindings: mediatek: Set min size for 'mediatek,pad-select'
      commit: d149dd2a806b9d11e570c3731eca8bda3c5f6238

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