linux-kernel - Re: [PATCH 1/1] ASoC: intel, keembay-i2s: Fix a dt_binding

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: <161729333651.31618.6325079972879808660.b4-ty@kernel.org>
Date:   Thu,  1 Apr 2021 17:15:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     devicetree <devicetree@...r.kernel.org>,
        alsa-devel <alsa-devel@...a-project.org>,
        Zhen Lei <thunder.leizhen@...wei.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 1/1] ASoC: intel, keembay-i2s: Fix a dt_binding_check warning

On Mon, 29 Mar 2021 16:14:35 +0800, Zhen Lei wrote:
> The property "dmas" contains two items: DMA "TX" and "RX" channel,
> Therefore, its value also needs to be written in two parts.
> 
> Otherwise, below YAML check warning is reported:
> Documentation/devicetree/bindings/sound/intel,keembay-i2s.example.dt.yaml:\
> i2s@...40000: dmas: [[4294967295, 29, 4294967295, 33]] is too short

Applied to

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

Thanks!

[1/1] ASoC: intel, keembay-i2s: Fix a dt_binding_check warning
      commit: 52cad756b777e82fabe05c728cc62b63b3c61fd3

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