From: blaisorblade@yahoo.it
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, blaisorblade@yahoo.it
Subject: [patch 1/1] Fix kconfig docs typo: integer -> int
Date: Thu, 10 Mar 2005 16:38:58 +0100 [thread overview]
Message-ID: <20050310153900.B75A56475@zion> (raw)
Trivial correction: the type of numbers for Kconfig is not integer but int (I
just verified because I followed the wrong docs and got a error, I looked
elsewhere and they are using int, and int works for me). Please apply.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
---
linux-2.6.11-paolo/Documentation/kbuild/kconfig-language.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -puN Documentation/kbuild/kconfig-language.txt~doc-big-typo-fix Documentation/kbuild/kconfig-language.txt
--- linux-2.6.11/Documentation/kbuild/kconfig-language.txt~doc-big-typo-fix 2005-03-10 16:35:38.000000000 +0100
+++ linux-2.6.11-paolo/Documentation/kbuild/kconfig-language.txt 2005-03-10 16:36:09.000000000 +0100
@@ -48,7 +48,7 @@ Menu attributes
A menu entry can have a number of attributes. Not all of them are
applicable everywhere (see syntax).
-- type definition: "bool"/"tristate"/"string"/"hex"/"integer"
+- type definition: "bool"/"tristate"/"string"/"hex"/"int"
Every config option must have a type. There are only two basic types:
tristate and string, the other types are based on these two. The type
definition optionally accepts an input prompt, so these two examples
@@ -100,7 +100,7 @@ applicable everywhere (see syntax).
symbols.
- numerical ranges: "range" <symbol> <symbol> ["if" <expr>]
- This allows to limit the range of possible input values for integer
+ This allows to limit the range of possible input values for int
and hex symbols. The user can only input a value which is larger than
or equal to the first symbol and smaller than or equal to the second
symbol.
_
next reply other threads:[~2005-03-14 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 15:38 blaisorblade [this message]
2005-03-17 21:20 ` 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=20050310153900.B75A56475@zion \
--to=blaisorblade@yahoo.it \
--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®