[PATCH] trivial: cpufreq-dt: correct dead link in documentation

[PATCH] trivial: cpufreq-dt: correct dead link in documentation

[Richard Genoud]

commit 3566c5b277a4 ("PM / OPP: Create a directory for opp bindings")
renamed the file:
Documentation/devicetree/bindings/power/opp.txt
to
Documentation/devicetree/bindings/opp/opp.txt
leaving a dead link in cpufreq/arm_big_little_dt.txt.

The link points now to the good file.

Signed-off-by: Richard Genoud <richard.genoud@gmail.com>
---
 Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
index e41c98ffbccb..dd3929e85dec 100644
--- a/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
+++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt
@@ -11,7 +11,7 @@ Required properties:
 - None
 
 Optional properties:
-- operating-points: Refer to Documentation/devicetree/bindings/power/opp.txt for
+- operating-points: Refer to Documentation/devicetree/bindings/opp/opp.txt for
   details. OPPs *must* be supplied either via DT, i.e. this property, or
   populated at runtime.
 - clock-latency: Specify the possible maximum transition latency for clock,

[PATCH] trivial: dt-bindings: correct path in documentation

[Richard Genoud]

As opp.txt was moved from:
Documentation/devicetree/bindings/power/
to
Documentation/devicetree/bindings/opp/
in the commit 3566c5b277a4 ("PM / OPP: Create a directory for opp
bindings"), the vendor bindings should also go in that directory.

Signed-off-by: Richard Genoud <richard.genoud@gmail.com>
---
 Documentation/devicetree/bindings/opp/opp.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt
index 0cb44dc21f97..f099d5d6f80d 100644
--- a/Documentation/devicetree/bindings/opp/opp.txt
+++ b/Documentation/devicetree/bindings/opp/opp.txt
@@ -51,7 +51,7 @@ accompanied by a corresponding "operating-points-names" property, to uniquely
 identify the OPP tables.
 
 If required, this can be extended for SoC vendor specfic bindings. Such bindings
-should be documented as Documentation/devicetree/bindings/power/<vendor>-opp.txt
+should be documented as Documentation/devicetree/bindings/opp/<vendor>-opp.txt
 and should have a compatible description like: "operating-points-v2-<vendor>".
 
 Optional properties: