From: Sean Wang <sean.w...@mediatek.com>

It should be good that no use "_" is in examples. Consequently,
those nodes in certain files which have an inappropriate name containing
"_" are all being replaced with "-".

Signed-off-by: Sean Wang <sean.w...@mediatek.com>
Cc: "Rafael J. Wysocki" <r...@rjwysocki.net>
Cc: Viresh Kumar <viresh.ku...@linaro.org>
Cc: Rob Herring <robh...@kernel.org>
Cc: Mark Rutland <mark.rutl...@arm.com>
Cc: linux...@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
 Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt 
b/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt
index d36f07e..38cfbb5 100644
--- a/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt
+++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek.txt
@@ -26,7 +26,7 @@ Optional properties:
 
 Example 1 (MT7623 SoC):
 
-       cpu_opp_table: opp_table {
+       cpu_opp_table: opp-table {
                compatible = "operating-points-v2";
                opp-shared;
 
@@ -86,7 +86,7 @@ Example 1 (MT7623 SoC):
        };
 
 Example 2 (MT8173 SoC):
-       cpu_opp_table_a: opp_table_a {
+       cpu_opp_table_a: opp-table-a {
                compatible = "operating-points-v2";
                opp-shared;
 
@@ -131,7 +131,7 @@ Example 2 (MT8173 SoC):
                };
        };
 
-       cpu_opp_table_b: opp_table_b {
+       cpu_opp_table_b: opp-table-b {
                compatible = "operating-points-v2";
                opp-shared;
 
-- 
2.7.4

Reply via email to