mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
	trivial@kernel.org
Subject: Re: [PATCH] Fix chapter reference in CodingStyle
Date: Wed, 25 Apr 2007 08:35:06 -0700	[thread overview]
Message-ID: <20070425083506.2a58c512.rdunlap@xenotime.net> (raw)
In-Reply-To: <200704231210.23105.jesper.juhl@gmail.com>

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 ***

      reply	other threads:[~2007-04-25 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 10:10 Jesper Juhl
2007-04-25 15:35 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070425083506.2a58c512.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®