From: Adrian Bunk <bunk@fs.tum.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: New kconfig: Please add define_*
Date: Thu, 21 Nov 2002 14:33:21 +0100 [thread overview]
Message-ID: <20021121133320.GD18869@fs.tum.de> (raw)
Hi Roman,
one thing that easily leads to errors is that the difference between
e.g. bool and define_bool is less obvious than before (it's no longer
explicitely stated). If there's no string behind the bool and no
"prompt" line it's now treated as define_bool. I've already found two
places in sound/oss/Kconfig where this was missing accidentially. Could
you add explicite define_* back to the config language and let the
program quit with an error if there's e.g. a define_bool with a string
or prompt line or a bool without a string or prompt line?
I know this requiress a conversion of several Kconfig files but
considering that this might prevent some confusion in the future I think
it's worth it.
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2002-11-21 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 13:33 Adrian Bunk [this message]
2002-11-21 16:55 ` Roman Zippel
2002-11-22 2:22 ` Miles Bader
2002-11-22 11:56 ` Roman Zippel
2002-11-23 12:39 ` Adrian Bunk
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=20021121133320.GD18869@fs.tum.de \
--to=bunk@fs.tum.de \
--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
all inboxes | Powered by JetHome®