diff --git a/[refs] b/[refs]
index 819d4cea083f..4d962829713d 100644
--- 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
index e7f5fc6ef20b..afc286775891 100644
--- 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