From: Tom Rini <trini@kernel.crashing.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where's the documentation for Kconfig?
Date: Fri, 1 Nov 2002 17:07:30 -0700 [thread overview]
Message-ID: <20021102000730.GB6410@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.44.0211020051090.6949-100000@serv>
On Sat, Nov 02, 2002 at 12:52:05AM +0100, Roman Zippel wrote:
> Hi,
>
> On Fri, 1 Nov 2002, Tom Rini wrote:
>
> > I want both of these statements to be legal:
> >
> > config HEXVAL_B
> > hex
> > depends on BAZ
> > default "0x12345678UL"
>
> Why?
Consistency with values? It's not needed, but in somplaces we had:
#define FOO 0x12345678UL,
which was replaced with
#define FOO CONFIG_BAR_VALUE
So for consistency (and only that really, so if it's hard just say No)
I'd like to be able to put back the 'UL' / 'L'
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-11-02 0:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 13:43 Where's the documentation for Kconfig? Matthew Wilcox
2002-10-31 14:43 ` Roman Zippel
2002-10-31 15:27 ` Christoph Hellwig
2002-10-31 16:03 ` Roman Zippel
2002-11-01 8:23 ` Rusty Russell
2002-11-01 12:52 ` Russell King
2002-11-01 13:50 ` Roman Zippel
2002-11-01 19:31 ` Russell King
2002-11-01 20:30 ` Tom Rini
2002-11-01 20:35 ` Russell King
2002-11-01 20:42 ` Tom Rini
2002-11-01 20:46 ` Russell King
2002-11-01 23:32 ` Tom Rini
2002-11-01 23:52 ` Roman Zippel
2002-11-02 0:07 ` Tom Rini [this message]
2002-11-02 0:46 ` Roman Zippel
2002-11-01 20:35 ` Roman Zippel
[not found] ` <20020625221306.GA439@free.fr>
[not found] ` <Pine.LNX.4.44.0211021254420.6949-100000@serv>
2002-11-02 13:20 ` Kconfig (qt) -> Gconfig (gtk+) Romain Lievin
2002-11-02 14:45 ` Roman Zippel
2002-11-02 18:56 ` qconf buglet James H. Cloos Jr.
2002-11-02 19:48 ` Roman Zippel
2002-11-02 23:40 ` James H. Cloos Jr.
2002-11-02 13:51 ` Where's the documentation for Kconfig? Erik Andersen
2002-11-02 19:26 ` Roman Zippel
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=20021102000730.GB6410@opus.bloom.county \
--to=trini@kernel.crashing.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 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.