aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/Documentation/devicetree/dynamic-resolution-notes.txt
diff options
context:
space:
mode:
authorHarish Jenny K N <harish_kandiga@mentor.com>2018-07-19 17:24:04 +0530
committerRob Herring <robh@kernel.org>2018-08-13 08:20:10 -0600
commitf11b9abc9318d5506f08156b4950c24e3cba73e5 (patch)
treed3cadce13ab5bf6ad02746241821fe2f91f0ff1b /Documentation/devicetree/dynamic-resolution-notes.txt
parentdt-bindings: Add Y Soft Corporation vendor prefix (diff)
downloadwireguard-linux-f11b9abc9318d5506f08156b4950c24e3cba73e5.tar.xz
wireguard-linux-f11b9abc9318d5506f08156b4950c24e3cba73e5.zip
Documentation: remove dynamic-resolution-notes reference to non-existent file
File dt-object-internal.txt does not exist. This patch removes a reference to it. Signed-off-by: Harish Jenny K N <harish_kandiga@mentor.com> Reviewed-by: Frank Rowand <frank.rowand@sony.com> Signed-off-by: Rob Herring <robh@kernel.org>
Diffstat (limited to 'Documentation/devicetree/dynamic-resolution-notes.txt')
-rw-r--r--Documentation/devicetree/dynamic-resolution-notes.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/Documentation/devicetree/dynamic-resolution-notes.txt b/Documentation/devicetree/dynamic-resolution-notes.txt
index 083d23262abe..c24ec366c5dc 100644
--- a/Documentation/devicetree/dynamic-resolution-notes.txt
+++ b/Documentation/devicetree/dynamic-resolution-notes.txt
@@ -2,15 +2,14 @@ Device Tree Dynamic Resolver Notes
----------------------------------
This document describes the implementation of the in-kernel
-Device Tree resolver, residing in drivers/of/resolver.c and is a
-companion document to Documentation/devicetree/dt-object-internal.txt[1]
+Device Tree resolver, residing in drivers/of/resolver.c
How the resolver works
----------------------
The resolver is given as an input an arbitrary tree compiled with the
proper dtc option and having a /plugin/ tag. This generates the
-appropriate __fixups__ & __local_fixups__ nodes as described in [1].
+appropriate __fixups__ & __local_fixups__ nodes.
In sequence the resolver works by the following steps: