Skip to contentSkip to conversation

Fix chapter reference in CodingStyle

PATCH In review Jesper Juhl 2 participants 2 messages Apr 23, 2007 – Apr 25, 2007 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Fix chapter reference in CodingStyle

Greetings,

commit 226a6b84aaaf1fac7a5d41cf4e7387fd9ba895d5 renumbered Chapter 11 in Documentation/CodingStyle to Chapter 12, but it didn't update the reference to that chapter further down in the file. This patch corrects the chapter reference.

---

 Documentation/CodingStyle |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Documentation/CodingStyle +1 -1
index 9069189..899777f 100644
@@ -625,7 +625,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
Acked-by on v1 1/1
#1 lore raw
Quoted 9 lines · On Mon, 23 Apr 2007 12:10:22 +0200 Jesper Juhl wrote:

Greetings,

commit 226a6b84aaaf1fac7a5d41cf4e7387fd9ba895d5 renumbered Chapter 11 in Documentation/CodingStyle to Chapter 12, but it didn't update the reference to that chapter further down in the file. This patch corrects the chapter reference.

Quoted 11 lines

---

 Documentation/CodingStyle |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Documentation/CodingStyle +0 -0
index 9069189..899777f 100644

Documentation/CodingStyle language. · line 631

Quoted 8 lines
Documentation/CodingStyle +1 -1
@@ -625,7 +625,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

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***