Having flash@0 in the binding example is misleading, because lookup is
global. Point that out explicitly and modify the example.
Signed-off-by: Ahmad Fatoum <ahmad@xxxxxx>
---
Documentation/devicetree/bindings/mtd/partition.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mtd/partition.rst b/Documentation/devicetree/bindings/mtd/partition.rst
index 6db54070a991..627b59eda04b 100644
--- a/Documentation/devicetree/bindings/mtd/partition.rst
+++ b/Documentation/devicetree/bindings/mtd/partition.rst
@@ -4,7 +4,7 @@ Representing flash partitions in devicetree
In addition to the upstream binding, another property is added:
Optional properties:
-- ``partuuid`` : The partition UUID for this partition.
+- ``partuuid`` : The global partition UUID for this partition.
Additionally, barebox also supports partitioning the eMMC boot partitions if
the partition table node is named appropriately:
@@ -16,7 +16,7 @@ Examples:
.. code-block:: none
- flash@0 {
+ / {
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
--
2.34.1
