<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/scripts/kconfig/confdata.c, branch v3.4.19</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/scripts/kconfig/confdata.c?h=v3.4.19</id>
<link rel='self' href='https://git.amat.us/linux/atom/scripts/kconfig/confdata.c?h=v3.4.19'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-04-13T01:35:58Z</updated>
<entry>
<title>kconfig: delete last traces of __enabled_ from autoconf.h</title>
<updated>2012-04-13T01:35:58Z</updated>
<author>
<name>Paul Gortmaker</name>
<email>paul.gortmaker@windriver.com</email>
</author>
<published>2012-04-12T23:46:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e4757cab4cff01e9c47b14376be7438694032c3c'/>
<id>urn:sha1:e4757cab4cff01e9c47b14376be7438694032c3c</id>
<content type='text'>
We've now fixed IS_ENABLED() and friends to not require any special
"__enabled_" prefixed versions of the normal Kconfig options, so delete
the last traces of them being generated.

Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Revert "kconfig: fix __enabled_ macros definition for invisible and un-selected symbols"</title>
<updated>2012-04-13T01:35:58Z</updated>
<author>
<name>Paul Gortmaker</name>
<email>paul.gortmaker@windriver.com</email>
</author>
<published>2012-04-12T23:46:33Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a959613533a176a8f5f402585827e94a5220d2db'/>
<id>urn:sha1:a959613533a176a8f5f402585827e94a5220d2db</id>
<content type='text'>
This reverts commit 953742c8fe8ac45be453fee959d7be40cd89f920.

Dumping two lines into autoconf.h for all existing Kconfig options
results in a giant file (~16k lines) we have to process each time we
compile something.  We've weaned IS_ENABLED() and similar off of
requiring the __enabled_ definitions so now we can revert the change
which caused all the extra lines.

Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>kconfig: fix new choices being skipped upon config update</title>
<updated>2012-01-26T10:01:56Z</updated>
<author>
<name>Arnaud Lacombe</name>
<email>lacombar@gmail.com</email>
</author>
<published>2012-01-23T22:29:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d09598d488f081e3be23f885ed65cbbe2d073b5'/>
<id>urn:sha1:5d09598d488f081e3be23f885ed65cbbe2d073b5</id>
<content type='text'>
Running `oldconfig' after any of the following configuration change:

either trivial addition, such as:

config A
	bool "A"

choice
	prompt "Choice ?"
	depends on A

	config CHOICE_B
		bool "Choice B"

	config CHOICE_C
		bool "Choice C"
endchoice

or more tricky change:

OLD KCONFIG                      |  NEW KCONFIG
                                 |
                                 |  config A
                                 |          bool "A"
                                 |
choice                           |  choice
        prompt "Choice ?"        |          prompt "Choice ?"
                                 |
        config CHOICE_C          |          config CHOICE_C
                bool "Choice C"  |                  bool "Choice C"
                                 |
        config CHOICE_D          |          config CHOICE_D
                bool "Choice D"  |                  bool "Choice D"
endchoice                        |
                                 |          config CHOICE_E
                                 |                  bool "Choice E"
                                 |                  depends on A
                                 |  endchoice

will not cause the choice to be considered as NEW, and thus not be
asked. The cause of this behavior is that choice's novelty are computed
statically right after the saved configuration has been read. At this
point, the new dependency's value is still unknown and asserted to be
`no'. Moreover, no update to this decision is made afterward.

Correct this by dynamically evaluating a choice's novelty, and removing the
static evaluation.

Reported-and-tested-by: Uwe Kleine-König &lt;u.kleine-koenig@pengutronix.de&gt;
Signed-off-by: Arnaud Lacombe &lt;lacombar@gmail.com&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>kconfig: use xfwrite wrapper function to silence warnings</title>
<updated>2011-12-18T20:54:12Z</updated>
<author>
<name>Peter Foley</name>
<email>pefoley2@verizon.net</email>
</author>
<published>2011-10-22T14:48:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=70cc01e7579cdb71f42f3f7085ab457be7808783'/>
<id>urn:sha1:70cc01e7579cdb71f42f3f7085ab457be7808783</id>
<content type='text'>
Use the xfwrite wrapper function defined in lkc.h to check the return value of
fwrite and silence these warnings.

  HOSTCC  scripts/kconfig/zconf.tab.o
scripts/kconfig/zconf.tab.c: In function 'header_print_comment':
/usr/src/lto/scripts/kconfig/confdata.c:551:10: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result
scripts/kconfig/zconf.tab.c: In function 'kconfig_print_comment':
/usr/src/lto/scripts/kconfig/confdata.c:467:10: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result

Signed-off-by: Peter Foley &lt;pefoley2@verizon.net&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>kconfig: fix __enabled_ macros definition for invisible and un-selected symbols</title>
<updated>2011-08-30T00:19:48Z</updated>
<author>
<name>Arnaud Lacombe</name>
<email>lacombar@gmail.com</email>
</author>
<published>2011-08-16T05:20:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=953742c8fe8ac45be453fee959d7be40cd89f920'/>
<id>urn:sha1:953742c8fe8ac45be453fee959d7be40cd89f920</id>
<content type='text'>
__enabled_&lt;sym-name&gt; are only generated on visible or selected entries, do not
reflect the purpose of its introduction.

Fix this by always generating these entries for named symbol.

Reported-by: Rabin Vincent &lt;rabin@rab.in&gt;
Signed-off-by: Arnaud Lacombe &lt;lacombar@gmail.com&gt;
</content>
</entry>
<entry>
<title>kconfig: Introduce IS_ENABLED(), IS_BUILTIN() and IS_MODULE()</title>
<updated>2011-07-29T19:53:30Z</updated>
<author>
<name>Michal Marek</name>
<email>mmarek@suse.cz</email>
</author>
<published>2011-07-20T15:38:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2a11c8ea20bf850b3a2c60db8c2e7497d28aba99'/>
<id>urn:sha1:2a11c8ea20bf850b3a2c60db8c2e7497d28aba99</id>
<content type='text'>
Replace the config_is_*() macros with a variant that allows for grepping
for usage of CONFIG_* options in the code. Usage:

  if (IS_ENABLED(CONFIG_NUMA))

or

  #if IS_ENABLED(CONFIG_NUMA)

The IS_ENABLED() macro evaluates to 1 if the argument is set (to either 'y'
or 'm'), IS_BUILTIN() tests if the option is 'y' and IS_MODULE() test if
the option is 'm'. Only boolean and tristate options are supported.

Reviewed-by: Arnaud Lacombe &lt;lacombar@gmail.com&gt;
Acked-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>kconfig: fix missing "0x" prefix from S_HEX symbol in autoconf.h</title>
<updated>2011-07-18T14:29:29Z</updated>
<author>
<name>Arnaud Lacombe</name>
<email>lacombar@gmail.com</email>
</author>
<published>2011-07-14T19:31:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eb4cf5a642f6430cffff7ba5d8d9bd46ea409281'/>
<id>urn:sha1:eb4cf5a642f6430cffff7ba5d8d9bd46ea409281</id>
<content type='text'>
The specialized printer for headers (espectially autoconf.h) is missing
fixup code for S_HEX symbol's "0x" prefix. As long as kconfig does not
warn for such missing prefix, this code is needed. Fix this.

In the same time, fix some nits in `header_print_symbol()'.

Cc: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Cc: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;

Broken-by: Arnaud Lacombe &lt;lacombar@gmail.com&gt;
Reported-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Reported-by: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;
Acked-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
Acked-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Signed-off-by: Arnaud Lacombe &lt;lacombar@gmail.com&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>kconfig: introduce specialized printer</title>
<updated>2011-07-01T14:23:27Z</updated>
<author>
<name>Arnaud Lacombe</name>
<email>lacombar@gmail.com</email>
</author>
<published>2011-05-16T03:42:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e54e692ba613c2170c66ce36a3791c009680af08'/>
<id>urn:sha1:e54e692ba613c2170c66ce36a3791c009680af08</id>
<content type='text'>
Make conf_write_symbol() grammar agnostic to be able to use it from different
code path. These path pass a printer callback which will print a symbol's name
and its value in different format.

conf_write_symbol()'s job become mostly only to prepare a string for the
printer. This avoid to have to pass specialized flag to generic
functions

Signed-off-by: Arnaud Lacombe &lt;lacombar@gmail.com&gt;
[mmarek: rebased on top of de12518 (kconfig: autogenerated config_is_xxx
macro)]
Signed-off-by: Michal Marek &lt;mmarek@suse.cz&gt;
</content>
</entry>
<entry>
<title>Merge branch 'kconfig-trivial' of git://github.com/lacombar/linux-2.6 into kbuild/kconfig</title>
<updated>2011-06-08T16:03:57Z</updated>
<author>
<name>Michal Marek</name>
<email>mmarek@suse.cz</email>
</author>
<published>2011-06-08T15:40:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=36fee53510f91d8ac5eb5dcba0e431a21ebdd5cd'/>
<id>urn:sha1:36fee53510f91d8ac5eb5dcba0e431a21ebdd5cd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kconfig: nuke LKC_DIRECT_LINK cruft</title>
<updated>2011-06-06T19:32:20Z</updated>
<author>
<name>Arnaud Lacombe</name>
<email>lacombar@gmail.com</email>
</author>
<published>2011-06-01T20:14:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5a6f8d2bd9e3392569ed6f29ea4d7210652f929b'/>
<id>urn:sha1:5a6f8d2bd9e3392569ed6f29ea4d7210652f929b</id>
<content type='text'>
This interface is not (and has never been ?) used by any frontend, just get rid
of it.

Signed-off-by: Arnaud Lacombe &lt;lacombar@gmail.com&gt;
</content>
</entry>
</feed>
