s/xen,shared-memory/xen,shared-memory-v1/g

The shared memory device tree binding went upstream as
"xen,shared-memory-v1". So, rename all occurrences of
"xen,shared-memory" to "xen,shared-memory-v1" in the docs.

Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>

diff --git a/docs/misc/arm/dom0_shared_mem.txt b/docs/misc/arm/dom0_shared_mem.txt
index 7b10444e061cc407537d21b8f8e7a6ba402bc672..1e2ba67e99cf09e30e520c61ff36a6db55c095ea 100644 (file)
--- a/docs/misc/arm/dom0_shared_mem.txt
+++ b/docs/misc/arm/dom0_shared_mem.txt
@@ -4,7 +4,7 @@ between dom0 and a domU.
 First, we have to add a reserved-memory node to the host device tree to
 advertise the special memory region to dom0, so that it won't use it to
 allocate memory as any other pages. For that, we can make use of the
-newly introduced "xen,shared-memory" compatible string. For example:
+newly introduced "xen,shared-memory-v1" compatible string. For example:
 
     reserved-memory {
         #address-cells = <0x2>;
@@ -12,7 +12,7 @@ newly introduced "xen,shared-memory" compatible string. For example:
         ranges;
 
         xen-shmem@0 {
-            compatible = "xen,shared-memory";
+            compatible = "xen,shared-memory-v1";
             reg = <0x0 0x70000000 0x0 0x1000>;
         };
     };
@@ -42,7 +42,7 @@ be for example:
             ranges;
 
             xen-shmem@0 {
-                compatible = "xen,shared-memory";
+                compatible = "xen,shared-memory-v1";
                 reg = <0x0 0x70000000 0x0 0x1000>;
             };
         };