From: dwalker@mvista.com
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Cc: sam@ravnborg.org
Cc: jengelh@gmx.de
Subject: [PATCH] docs: small kbuild cleanup
Date: Sun, 01 Oct 2006 09:01:30 -0700 [thread overview]
Message-ID: <20061001160130.326875000@mvista.com> (raw)
While reading this I noticed that the contents of this document
list section "3.8 Command line dependency" but it doesn't exist
in the document.
Signed-Off-By: Daniel Walker <dwalker@mvista.com>
---
Documentation/kbuild/kconfig-language.txt | 2 +-
Documentation/kbuild/makefiles.txt | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6.18/Documentation/kbuild/kconfig-language.txt
===================================================================
--- linux-2.6.18.orig/Documentation/kbuild/kconfig-language.txt
+++ linux-2.6.18/Documentation/kbuild/kconfig-language.txt
@@ -1,7 +1,7 @@
Introduction
------------
-The configuration database is collection of configuration options
+The configuration database is a collection of configuration options
organized in a tree structure:
+- Code maturity level options
Index: linux-2.6.18/Documentation/kbuild/makefiles.txt
===================================================================
--- linux-2.6.18.orig/Documentation/kbuild/makefiles.txt
+++ linux-2.6.18/Documentation/kbuild/makefiles.txt
@@ -390,7 +390,7 @@ more details, with real examples.
The kernel may be built with several different versions of
$(CC), each supporting a unique set of features and options.
kbuild provide basic support to check for valid options for $(CC).
- $(CC) is useally the gcc compiler, but other alternatives are
+ $(CC) is usually the gcc compiler, but other alternatives are
available.
as-option
--
reply other threads:[~2006-10-01 16:05 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=20061001160130.326875000@mvista.com \
--to=dwalker@mvista.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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®