mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New kconfig: Please add define_*
Date: Thu, 21 Nov 2002 17:55:42 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211211740130.2113-100000@serv> (raw)
In-Reply-To: <20021121133320.GD18869@fs.tum.de>

Hi,

On Thu, 21 Nov 2002, Adrian Bunk wrote:

> 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?

It was not missing accidentially, these symbols were defined with 
define_bool before.
I'll think about the define_* syntax, but I will not make the other syntax 
illegal. The current 'bool "prompt"' is already a shortcut for the more 
common requirement:

config FOO
	bool
	prompt '...'

Also note that the role of the default has changed, a default cannot 
override a prompt anymore (it only provides a default value to the 
prompt). The define_* syntax might imply that this is possible, but it 
won't.

bye, Roman


  reply	other threads:[~2002-11-21 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 13:33 Adrian Bunk
2002-11-21 16:55 ` Roman Zippel [this message]
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=Pine.LNX.4.44.0211211740130.2113-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=bunk@fs.tum.de \
    --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®