All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Martin Walch <walch.martin@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	Randy Dunlap <rdunlap@xenotime.net>,
	Arnaud Lacombe <lacombar@gmail.com>
Subject: Re: Documentation of kconfig language differs from implementation regarding existence of symbols
Date: Thu, 11 Oct 2012 22:27:36 +0200	[thread overview]
Message-ID: <50772BB8.6080404@suse.cz> (raw)
In-Reply-To: <1940598.VZE8PFWQyj@tacticalops>

Dne 10.10.2012 02:17, Martin Walch napsal(a):
> The file linux/Documentation/kbuild/kconfig-language.txt says:
> 
>> The following two methods produce the same kconfig symbol
>> dependencies but differ greatly in kconfig symbol existence
>> (production) in the generated config file.
>> 
>> case 1:
>> 
>> config FOO tristate "about foo" depends on BAR
>> 
>> vs. case 2:
>> 
>> if BAR config FOO tristate "about foo" endif
>> 
>> In case 1, the symbol FOO will always exist in the config file
>> (given no other dependencies).  In case 2, the symbol FOO will
>> only exist in the config file if BAR is enabled.
> 
> However, I can not reproduce this. The attached file contains both
> cases. When running make menuconfig, setting BAR0 and BAR1 both to
> n, and saving the configuration, there is neither FOO0 nor FOO1 in
> the resulting configuration file.

Indeed, that paragraph seems wrong. I think we should revert commit
64b81ed. Randy, Arnaud?

Thanks,
Michal


  reply	other threads:[~2012-10-11 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  0:17 Documentation of kconfig language differs from implementation regarding existence of symbols Martin Walch
2012-10-11 20:27 ` Michal Marek [this message]
2012-10-11 20:44   ` Yann E. MORIN

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=50772BB8.6080404@suse.cz \
    --to=mmarek@suse.cz \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=walch.martin@gmx.de \
    /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.