[PATCH] Fix chapter reference in CodingStyle

[PATCH] Fix chapter reference in CodingStyle

[Jesper Juhl]

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.


Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
--- 

 Documentation/CodingStyle |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index 9069189..899777f 100644
--- a/Documentation/CodingStyle
+++ b/Documentation/CodingStyle
@@ -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

Re: [PATCH] Fix chapter reference in CodingStyle

[Randy Dunlap]

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.
> 
> 
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

> --- 
> 
>  Documentation/CodingStyle |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
> index 9069189..899777f 100644
> --- a/Documentation/CodingStyle
> +++ b/Documentation/CodingStyle
> @@ -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 ***