From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] new kconfig goodies
Date: Mon, 12 May 2003 17:13:55 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.21.0305121712310.11877-100000@vervain.sonytel.be> (raw)
In-Reply-To: <Pine.LNX.4.44.0305111838300.14274-100000@serv>
On Mon, 12 May 2003, Roman Zippel wrote:
> 3. Finally I added support for ranges, so that this becomes possible:
>
> config LOG_BUF_SHIFT
> int "Kernel log buffer size" if DEBUG_KERNEL
> range 10 20
> ...
>
> Right now this is only used to check the direct user input, this means
> directly editing .config will ignore the range (please don't rely on this
> feature :) ).
I hope `make oldconfig' also checks the range? Imagine ranges being changed in
the Kconfig file.
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:[~2003-05-12 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 13:39 [PATCH] new kconfig goodies Roman Zippel
2003-05-12 14:16 ` Adrian Bunk
2003-05-12 15:37 ` Roman Zippel
2003-05-12 14:32 ` Dave Jones
2003-05-12 15:39 ` Roman Zippel
2003-05-12 16:08 ` Dave Jones
2003-05-12 16:00 ` Tomas Szepe
2003-05-12 22:36 ` Roman Zippel
2003-05-12 15:13 ` Geert Uytterhoeven [this message]
2003-05-12 15:43 ` Roman Zippel
2003-05-13 1:38 ` Miles Bader
2003-05-13 1:44 ` Miles Bader
2003-05-13 15:27 ` Roman Zippel
2003-05-13 21:17 ` Miles Bader
2003-05-14 19:51 ` Roman Zippel
2003-05-14 20:56 ` Andreas Schwab
2003-05-14 22:11 ` Roman Zippel
2003-05-15 0:21 ` Michael Alan Dorman
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.GSO.4.21.0305121712310.11877-100000@vervain.sonytel.be \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).