public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yang Rui Rui <ruirui.r.yang@tieto.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Randy Dunlap <rdunlap@xenotime.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH] docs: INSTALL_HDR_PATH fix
Date: Fri, 19 Nov 2010 13:54:39 +0800	[thread overview]
Message-ID: <4CE6111F.5070303@tieto.com> (raw)

INSTALL_HDR_PATH example in documentation is wrong.
it should be a prefix like /usr

Signed-off-by: Yang Ruirui<ruirui.r.yang@tieto.com>
---
  Documentation/make/headers_install.txt |    4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-2.6.37-rc2.orig/Documentation/make/headers_install.txt	2010-11-16 10:31:02.000000000 +0800
+++ linux-2.6.37-rc2/Documentation/make/headers_install.txt	2010-11-19 12:30:09.000000000 +0800
@@ -24,7 +24,7 @@ The "make headers_install" command can b
  kernel source code (or using a standard out-of-tree build).  It takes two
  optional arguments:
  
-  make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr/include
+  make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr
  
  ARCH indicates which architecture to produce headers for, and defaults to the
  current architecture.  The linux/asm directory of the exported kernel headers
@@ -34,7 +34,7 @@ the command:
    ls -d include/asm-* | sed 's/.*-//'
  
  INSTALL_HDR_PATH indicates where to install the headers.  It defaults to
-"./usr/include".
+"./usr".
  
  The command "make headers_install_all" exports headers for all architectures
  simultaneously.  (This is mostly of interest to distribution maintainers,

-- 
To adhere means to yield. To yield means to adhere.

                 reply	other threads:[~2010-11-19  5:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CE6111F.5070303@tieto.com \
    --to=ruirui.r.yang@tieto.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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