| commit | 43d1b6518e523df1bd15f07be480d10a9eb043bc | |
| author | Steven Rostedt <srostedt@redhat.com> | |
| Sat, 16 Jul 2011 02:01:56 +0000 (15 22:01 -0400) | ||
| committer | Steven Rostedt <rostedt@goodmis.org> | |
| Sat, 16 Jul 2011 02:01:56 +0000 (15 22:01 -0400) | ||
| tree | 8362aa52fae89d8933839b9e47fca761f4494f43 | treesnapshot (tar.gz zip) |
| parent | 35ce5952e62bc72520e6a7dbcfa4baf8c9f9eedb | commitdiff |
ktest: Keep fonud configs separate from default configs
The IGNORE_CONFIG file holds the configs that we don't want to change
(with their proper settings). But on start up, the make noconfig is
executed, and the configs that are on are also put into the ignore
config category. But these are configs that were forced on by the
kconfig scripts and not something that we found must be enabled to boot
our machine. By keeping the configs that are forced on by default,
separate from the configs we found that are required to boot the box, we
can get a much more interesting IGNORE_CONFIG. In fact, the
IGNORE_CONFIG can usually end up being the must have configs to boot,
and only have 6 or 7 configs set.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
The IGNORE_CONFIG file holds the configs that we don't want to change
(with their proper settings). But on start up, the make noconfig is
executed, and the configs that are on are also put into the ignore
config category. But these are configs that were forced on by the
kconfig scripts and not something that we found must be enabled to boot
our machine. By keeping the configs that are forced on by default,
separate from the configs we found that are required to boot the box, we
can get a much more interesting IGNORE_CONFIG. In fact, the
IGNORE_CONFIG can usually end up being the must have configs to boot,
and only have 6 or 7 configs set.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
| tools/testing/ktest/ktest.pl | diffblobblamehistory |