From: Richard Genoud <richard.genoud@gmail.com>
To: Jiri Kosina <trivial@kernel.org>
Cc: linux-kernel@vger.kernel.org, Richard Genoud <richard.genoud@gmail.com>
Subject: [PATCH] trivial: dt-bindings: correct path in documentation
Date: Tue, 3 Nov 2015 13:09:24 +0100 [thread overview]
Message-ID: <1446552564-3750-2-git-send-email-richard.genoud@gmail.com> (raw)
In-Reply-To: <1446552564-3750-1-git-send-email-richard.genoud@gmail.com>
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:
prev parent reply other threads:[~2015-11-03 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 12:09 [PATCH] trivial: cpufreq-dt: correct dead link " Richard Genoud
2015-11-03 12:09 ` Richard Genoud [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446552564-3750-2-git-send-email-richard.genoud@gmail.com \
--to=richard.genoud@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®