---

yaml --- r: 54713 b: refs/heads/master c: 53ab97a h: refs/heads/master i: 54711: 512ee52 v: v3
git-mirror · May 8, 2007 · 481b5c1 · 481b5c1
1 parent 69c0277
commit 481b5c1
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 4f99ed67cc1cf5302ea18aa042d75641b61a0a1b
+refs/heads/master: 53ab97a1c1536015d4d6d900363ea96fece5ed97
diff --git a/trunk/Documentation/CodingStyle b/trunk/Documentation/CodingStyle
@@ -640,7 +640,7 @@ language.
 
 There appears to be a common misperception that gcc has a magic "make me
 faster" speedup option called "inline". While the use of inlines can be
-appropriate (for example as a means of replacing macros, see Chapter 11), it
+appropriate (for example as a means of replacing macros, see Chapter 12), it
 very often is not. Abundant use of the inline keyword leads to a much bigger
 kernel, which in turn slows the system as a whole down, due to a bigger
 icache footprint for the CPU and simply because there is less memory