diff options
| author | Jesper Juhl | 2007-05-08 00:31:06 -0700 |
|---|---|---|
| committer | Linus Torvalds | 2007-05-08 11:15:13 -0700 |
| commit | 53ab97a1c1536015d4d6d900363ea96fece5ed97 (patch) | |
| tree | d56c8d674a3027983ab8ea46f3779dca003c2091 /Documentation/CodingStyle | |
| parent | 4f99ed67cc1cf5302ea18aa042d75641b61a0a1b (diff) | |
Fix chapter reference in CodingStyle
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.
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/CodingStyle')
| -rw-r--r-- | Documentation/CodingStyle | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle index e7f5fc6ef20b..afc286775891 100644 --- a/Documentation/CodingStyle +++ b/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 |