linux-kernel - Re: [PATCH] ASoC: dt-bindings: rt5682s: correct several errors

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:   Mon, 20 Sep 2021 16:30:49 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Derek Fang <derek.fang@...ltek.com>, devicetree@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
        linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        alsa-devel@...a-project.org
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] ASoC: dt-bindings: rt5682s: correct several errors

On Mon, 20 Sep 2021 13:21:06 +0200, Krzysztof Kozlowski wrote:
> Correct several errors in rt5682s dtschema:
> 1. The examples should be under "examples":
>     'example' is not one of ['$id', '$schema', 'title', 'description', 'examples', ...
> 
> 2. Missing type for vendor properties
> 
> 3. clock-names should be an array:
>     properties:clock-names:items: {'const': 'mclk'} is not of type 'array'
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: rt5682s: correct several errors
      commit: a7a18abbd26caf22e40165eb734e67d338735f5b

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