From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] cc-cross-prefix spelling (was: Re: [GI:wqT PULL] kbuild updates - second round)
Date: Sun, 21 Oct 2007 19:55:00 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710211953550.6155@anakin> (raw)
In-Reply-To: <20071019204415.GA623@uranus.ravnborg.org>
On Fri, 19 Oct 2007, Sam Ravnborg wrote:
> The cc-cross-prefix is new and developed on request from Geert Uytterhoeven.
Spelling fixes for cc-cross-prefix documentation
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
Documentation/kbuild/makefiles.txt | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
--- a/Documentation/kbuild/makefiles.txt
+++ b/Documentation/kbuild/makefiles.txt
@@ -519,17 +519,17 @@ more details, with real examples.
to the user why it stops.
cc-cross-prefix
- cc-cross-prefix is used to check if there exist a $(CC) in path with
+ cc-cross-prefix is used to check if there exists a $(CC) in path with
one of the listed prefixes. The first prefix where there exist a
prefix$(CC) in the PATH is returned - and if no prefix$(CC) is found
then nothing is returned.
Additional prefixes are separated by a single space in the
call of cc-cross-prefix.
- This functionality is usefull for architecture Makefile that try
- to set CROSS_COMPILE to well know values but may have several
+ This functionality is useful for architecture Makefiles that try
+ to set CROSS_COMPILE to well-known values but may have several
values to select between.
- It is recommended only to try to set CROSS_COMPILE is it is a cross
- build (host arch is different from target arch). And is CROSS_COMPILE
+ It is recommended only to try to set CROSS_COMPILE if it is a cross
+ build (host arch is different from target arch). And if CROSS_COMPILE
is already set then leave it with the old value.
Example:
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2007-10-21 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 20:44 [GI:wqT PULL] kbuild updates - second round Sam Ravnborg
2007-10-21 17:55 ` Geert Uytterhoeven [this message]
2007-10-21 18:58 ` [PATCH] cc-cross-prefix spelling (was: Re: [GI:wqT PULL] kbuild updates - second round) Sam Ravnborg
2007-10-21 17:57 ` [PATCH] m68k: Use cc-cross-prefix " Geert Uytterhoeven
2007-10-21 18:22 ` Sam Ravnborg
2007-10-21 18:29 ` Geert Uytterhoeven
2007-10-22 1:07 ` Kolbjørn Barmen
2007-10-22 7:16 ` Geert Uytterhoeven
2007-10-22 8:09 ` Kolbjørn Barmen
2007-10-22 9:13 ` Andreas Schwab
2007-10-22 18:36 ` Geert Uytterhoeven
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=Pine.LNX.4.64.0710211953550.6155@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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®