public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Randy Dunlap <rddunlap@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: Difference between select and enable in Kconfig
Date: Sun, 21 Dec 2003 18:22:06 +0100	[thread overview]
Message-ID: <1072027326.2684.72.camel@pegasus> (raw)
In-Reply-To: <20031220205433.195037e8.rddunlap@osdl.org>

Hi Randy,

> | while porting some of my drivers to 2.6 which use the firmware loader
> | for example I came to the question whether to use select or enable to
> | achieve the desired result. Looking at the documention don't gives me
> | the answer and from zconf.l I feel that both options are the same. Can
> | anyone please explain me the differences if there are any?
> 
> I agree, they look like synonyms.
> There's nothing about "enable" in Documentation/kbuild/kconfig-language.txt
> and there's evidence in zconf.l (as you mention) and in menu.c
> that they are the same:
> 
> 			case P_SELECT:
> 				sym2 = prop_get_symbol(prop);
> 				if ((sym->type != S_BOOLEAN && sym->type != S_TRISTATE) ||
> 				    (sym2->type != S_BOOLEAN && sym2->type != S_TRISTATE))
> 					fprintf(stderr, "%s:%d:warning: enable is only allowed with boolean and tristate symbols\n",
> 					                                ~~~~~~

so both options achieve the same result. Why do we have two different
options for the same stuff? Should we not remove one?

Regards

Marcel



  reply	other threads:[~2003-12-21 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21  2:46 Difference between select and enable in Kconfig Marcel Holtmann
2003-12-21  4:54 ` Randy.Dunlap
2003-12-21 17:22   ` Marcel Holtmann [this message]
2003-12-21 17:34     ` Roman Zippel
2003-12-21 18:06       ` Marcel Holtmann

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=1072027326.2684.72.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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