From: Rob Landley <rob@landley.net>
To: akpm@linux-foundation.org
Cc: matthew@wil.cx, alan@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH] Add recommended section IDs to deviceiobook.tmpl
Date: Tue, 9 Oct 2007 02:35:07 -0500 [thread overview]
Message-ID: <200710090235.08063.rob@landley.net> (raw)
From: Rob Landley <rob@landley.net>
Add recommended section ID tags to deviceiobook.tmpl
Signed-off-by: Rob Landley <rob@landley.net>
---
Because otherwise the link #anchors in the html vary from build to build.
Documentation/DocBook/deviceiobook.tmpl | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff -r a26a53ed1101 Documentation/DocBook/deviceiobook.tmpl
--- a/Documentation/DocBook/deviceiobook.tmpl Sun Oct 07 16:42:22 2007 -0700
+++ b/Documentation/DocBook/deviceiobook.tmpl Tue Oct 09 02:32:12 2007 -0500
@@ -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(&dev_
</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(&dev_
</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
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
reply other threads:[~2007-10-09 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200710090235.08063.rob@landley.net \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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