linux-kernel - Re: [PATCH v3 0/2] ASoC: dt-bindings: atmel-classd: Convert to

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: <165834618426.685508.3523782122255231487.b4-ty@kernel.org>
Date:   Wed, 20 Jul 2022 20:43:04 +0100
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, nicolas.ferre@...rochip.com,
        Ryan.Wanner@...rochip.com, alexandre.belloni@...tlin.com,
        krzysztof.kozlowski+dt@...aro.org, claudiu.beznea@...rochip.com,
        lgirdwood@...il.com
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH v3 0/2] ASoC: dt-bindings: atmel-classd: Convert to

On Fri, 15 Jul 2022 09:29:20 -0700, Ryan.Wanner@...rochip.com wrote:
> From: Ryan Wanner <Ryan.Wanner@...rochip.com>
> 
> This patch series converts atmel-classd and atmel-pdmic device tree
> bindings to json-schema.
> 
> v1 -> v2:
> - Fix commit formatting.
> - Fix titles in yaml file.
> - Removed trivial descriptions.
> - Correct formatting errors.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: atmel-classd: Convert to json-schema
      commit: a3b19e0c9cdd0ece48f34f68f922764f26435f73
[2/2] ASoC: dt-bindings: atmel-classd: PDMIC convert to json-schema
      commit: ca0e30b19dbe5f23cf0abe047259a9e9495624c6

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