tag 3e4892e9201af46ba6df30b7bb8925da06f28cbc
tagger Steven Rostedt <rostedt@rostedt.homelinux.com> Mon Jan 20 10:28:56 2014 -0500
object 95edca5c523c4b404dd60baa0a1bea0e4c38fd72

While debugging the problem with localmodconfig and the ALSA codec
modules all being set, I discovered a small bug in the dependency
logic.

If a config has a dependency based on its setting value, localmodcondig
misses it.

For example:

config FOO
    default y if BAR || ZOO

If FOO is needed for a module and is set to '=m', and so are BAR or ZOO,
localmodconfig will not see that BAR or ZOO are also needed for the foo
module, and will incorrectly disable them.

commit 95edca5c523c4b404dd60baa0a1bea0e4c38fd72
author Steven Rostedt (Red Hat) <rostedt@goodmis.org> Wed Dec 18 12:35:20 2013 -0500
committer Steven Rostedt <rostedt@goodmis.org> Fri Dec 20 17:02:44 2013 -0500
tree 7172ab3dff7dc0a3751d5c1e8c31599930422837
parent 319e2e3f63c348a9b66db4667efa73178e18b17d

localmodconfig: Add config depends by default settings

Currently localmodconfig will miss dependencies from the default option.
For example:

config FOO
	default y if BAR || ZOO

If FOO is needed for a module and is set to '=m', and so are BAR or ZOO,
localmodconfig will not see that BOO or ZOO are also needed for the foo
module, and will incorrectly disable them.

Link: http://lkml.kernel.org/r/20131218175137.162937350@goodmis.org

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>