From: Kristian Edlund <edlund@groenstue.dk>
To: trivial@rustcorp.com.au
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Typos in Documation/kbuild/modules.txt 2.6.15-rc2
Date: Tue, 22 Nov 2005 14:08:06 +0100 [thread overview]
Message-ID: <43831836.3040505@groenstue.dk> (raw)
From: Kristian Edlund <edlund@groenstue.dk>
I found a few typos, in Documentation/kbuild/modules.txt
I also changes the $PWD to `pwd` for consistency throughout the document.
Signed-off-by: Kristian Edlund <edlund@groenstue.dk>
---
I am not sure this is the right place to post, but now I am trying
anyway. If I am completly wrong and changes to documentation should not
be sent here, could please help me a bit with where I should send it.
--- Documentation/kbuild/modules.txt.orig 2005-11-22
03:47:12.000000000 +0100
+++ Documentation/kbuild/modules.txt 2005-11-22 03:11:13.000000000 +0100
@@ -38,8 +38,8 @@ included in the kernel tree.
What is covered within this file is mainly information to authors
of modules. The author of an external modules should supply
a makefile that hides most of the complexity so one only has to type
-'make' to buld the module. A complete example will be present in
-chapter ¤. Creating a kbuild file for an external module".
+'make' to build the module. A complete example will be present in
+chapter 4. Creating a kbuild file for an external module".
=== 2. How to build external modules
@@ -84,14 +84,14 @@ when building an external module.
Same functionality as if no target was specified.
See description above.
- make -C $KDIR M=$PWD modules_install
+ make -C $KDIR M=`pwd` modules_install
Install the external module(s).
Installation default is in /lib/modules/<kernel-version>/extra,
- but may be prefixed with INSTALL_MOD_PATH - see separate chater.
+ but may be prefixed with INSTALL_MOD_PATH - see separate chapter.
- make -C $KDIR M=$PWD clean
+ make -C $KDIR M=`pwd` clean
Remove all generated files for the module - the kernel
- source directory is not moddified.
+ source directory is not modified.
make -C $KDIR M=`pwd` help
help will list the available target when building external
@@ -99,8 +99,6 @@ when building an external module.
--- 2.3 Available options:
- $KDIR refer to path to kernel src
-
make -C $KDIR
Used to specify where to find the kernel source.
'$KDIR' represent the directory where the kernel source is.
@@ -341,7 +339,7 @@ directory and therefore needs to deal wi
EXTRA_CFLAGS := -Iinclude
8123-y := 8123_if.o 8123_pci.o 8123_bin.o
- Note that in the assingment there is no space between -I and the path.
+ Note that in the assignment there is no space between -I and the path.
This is a kbuild limitation and no space must be present.
next reply other threads:[~2005-11-22 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 13:08 Kristian Edlund [this message]
2005-11-22 16:56 ` [PATCH] Typos in Documation/kbuild/modules.txt 2.6.15-rc2 Linus Torvalds
2005-11-22 22:02 ` Kristian Edlund
2005-11-22 22:08 ` Sam Ravnborg
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=43831836.3040505@groenstue.dk \
--to=edlund@groenstue.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=trivial@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.