From: Roman Zippel <zippel@linux-m68k.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where's the documentation for Kconfig?
Date: Fri, 1 Nov 2002 21:35:47 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0211012119290.6949-100000@serv> (raw)
In-Reply-To: <20021101193112.B26989@flint.arm.linux.org.uk>
Hi,
On Fri, 1 Nov 2002, Russell King wrote:
> Ok, next problem.
>
> A "hex" config entry under the old config language used to omit the "0x"
> prefix, requiring it to be added by whatever used it. Kconfig adds the
> "0x" prefix, thereby causing errors.
>
> Is this difference intentional?
No, but looking at it, I think it's better to fix the few users and to
keep it common instead. Is there anything that needs the numbers without
the prefix?
bye, Roman
next prev parent reply other threads:[~2002-11-01 20:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 13:43 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
2002-11-02 0:46 ` Roman Zippel
2002-11-01 20:35 ` Roman Zippel [this message]
[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=Pine.LNX.4.44.0211012119290.6949-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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®