[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174060289250.139585.8159041053673503341.b4-ty@kernel.org>
Date: Wed, 26 Feb 2025 20:48:12 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org,
Vincenzo Frascino <vincenzo.frascino@....com>
Cc: Maruthi Srinivas Bayyavarapu <maruthi.srinivas.bayyavarapu@...inx.com>,
Sudeep Holla <sudeep.holla@....com>, Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 0/4] xlnx: dt-bindings: Convert to json-schema
On Wed, 26 Feb 2025 12:23:21 +0000, Vincenzo Frascino wrote:
> This series converts the folling Xilinx device tree binding documentation:
> - xlnx,i2s
> - xlnx,audio-formatter
> - xlnx,spdif
> to json-schema.
>
> To simplify the testing a linux tree rebased on 6.13-rc4 is accessible
> at [1].
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: dt-bindings: xlnx,i2s: Convert to json-schema
commit: a206376b425472c7c3a824f47a9967a4c97ae32c
[2/4] ASoC: dt-bindings: xlnx,audio-formatter: Convert to json-schema
commit: 1b8b6dd0c91b7db58e344f01781932458ac43da3
[3/4] ASoC: dt-bindings: xlnx,spdif: Convert to json-schema
commit: 7ed7065dfbbac1b5405a0c8029299847e408cf97
[4/4] MAINTAINERS: Add Vincenzo Frascino as Xilinx Sound Driver Maintainer
commit: 55a1abd6e76ce91eb6049f32efec3a8506686748
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
Powered by blists - more mailing lists