Skip to contentSkip to conversation

ASoC: dt-bindings: maxim,max9867: fix example

PATCH In review Richard Leitner 3 participants 3 messages Mar 28, 2023

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ASoC: dt-bindings: maxim,max9867: fix example

Remove the common clock node from the example as suggested by Krzysztof Kozlowski in [1].

[1] https://lore.kernel.org/lkml/[email protected]/

---
 Documentation/devicetree/bindings/sound/maxim,max9867.yaml | 6 ------
 1 file changed, 6 deletions(-)
Documentation/devicetree/bindings/sound/maxim,max9867.yaml +0 -6
index 6f27029b137d..0b9a84d33b6c 100644
@@ -57,10 +57,4 @@ examples:
             clocks = <&codec_clk>;
         };
     };
-
-    codec_clk: clock {
-        compatible = "fixed-clock";
-        #clock-cells = <0>;
-        clock-frequency = <12288000>;
-    };
 ...

---
base-commit: ad58151fa04280a938c173bcba05ba42a4073d92
change-id: 20230328-max9867_dt_example_fix-e136f2a4da25

Best regards,

Signature · 1 line
Richard Leitner <[email protected]>
maintainer
#2 lore raw
In reply to Richard Leitner
Quoted 6 lines · Richard Leitner

Remove the common clock node from the example as suggested by Krzysztof Kozlowski in [1].

[1] https://lore.kernel.org/lkml/[email protected]/

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: maxim,max9867: fix example

      commit: d23d50de4ad9a960b752b8b7f4ffce32e05a8971

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