ASoC: dt-bindings: rt1015p: add new compatible id
Subsystems (2)
PATCH 2/2 ASoC: dt-bindings: rt1015p: add new compatible id
Add new compatible ID for rt1015p in dt-bindings document.
--- Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml +3 -1
@@ -15,7 +15,9 @@ description: | properties: compatible: - const: realtek,rt1015p + oneOf: + const: realtek,rt1015p + const: realtek,rt1019p sdb-gpios: description:
Signature · 1 line
2.31.1
Rob Herring
maintainerQuoted 2 lines · Jack Yu
Add new compatible ID for rt1015p in dt-bindings document.
Please resend without the winmail.dat attachment. And run 'make dt_binding_check' as this will fail.
Quoted 24 lines
Signed-off-by Jack Yu <[email protected]>--- Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)Documentation/devicetree/bindings/sound/realtek,rt1015p.yaml +3
-2@@ -15,7 +15,9 @@ description: | properties: compatible: - const: realtek,rt1015p + oneOf: + const: realtek,rt1015p + const: realtek,rt1019p sdb-gpios: description: --2.31.1
Mark Brown
maintainerQuoted 5 lines · Jack Yu
Add new compatible ID for rt1015p in dt-bindings document.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[2/2] ASoC: dt-bindings: rt1015p: add new compatible id
commit: 064478e4877c76b0c1fd1155934f226f1561aab3
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