---

yaml
---
r: 70799
b: refs/heads/master
c: 541ceb3
h: refs/heads/master
i:
  70797: b76f0c1
  70795: d9f488d
  70791: 677f604
  70783: 8431834
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 8d63494f780a77f3edfe9b470d65b7f265ae8d5a
+refs/heads/master: 541ceb359e3fb2714bf7a9fa3c134ce3e29f427a

trunk/Documentation/DocBook/deviceiobook.tmpl

@@ -85,7 +85,7 @@
 
   <chapter id="mmio">
     <title>Memory Mapped IO</title>
-    <sect1>
+    <sect1 id="getting_access_to_the_device">
       <title>Getting Access to the Device</title>
       <para>
 	The most widely supported form of IO is memory mapped IO.
@@ -114,7 +114,7 @@
       </para>
     </sect1>
 
-    <sect1>
+    <sect1 id="accessing_the_device">
       <title>Accessing the device</title>
       <para>
 	The part of the interface most used by drivers is reading and
@@ -272,9 +272,9 @@ CPU B:  spin_unlock_irqrestore(&amp;dev_lock, flags)
 
   </chapter>
 
-  <chapter>
+  <chapter id="port_space_accesses">
     <title>Port Space Accesses</title>
-    <sect1>
+    <sect1 id="port_space_explained">
       <title>Port Space Explained</title>
 
       <para>
@@ -291,7 +291,7 @@ CPU B:  spin_unlock_irqrestore(&amp;dev_lock, flags)
       </para>
 
     </sect1>
-    <sect1>
+    <sect1 id="accessing_port_space">
       <title>Accessing Port Space</title>
       <para>
 	Accesses to this space are provided through a set of functions