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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue,  3 Nov 2015 13:09:24 +0100
From:	Richard Genoud <richard.genoud@...il.com>
To:	Jiri Kosina <trivial@...nel.org>
Cc:	linux-kernel@...r.kernel.org,
	Richard Genoud <richard.genoud@...il.com>
Subject: [PATCH] trivial: dt-bindings: correct path in documentation

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@...il.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:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/