| Age | Commit message (Collapse) | Author |
|---|
|
Upstream is dropping support for is not set, so we adjust our
configs accordingly.
Commit:
https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git/commit/?h=for-next&id=55de8686df7ed2b5237867b130e30c728bbd9db4
kconfig: change .config format to use =n instead of "is not set"
The .config file uses "# CONFIG_FOO is not set" form to represent
disabled options. In the old days, it was useful because the .config
was directly included from Makefiles. For example, you can use
"ifdef CONFIG_FOO" in Makefiles to check if the option is enabled.
Commit c955ccafc38e ("kconfig: fix .config dependencies") introduced
include/config/auto.conf, which mirrors the .config, but trims down
all disabled options.
Since then, include/config/auto.conf defines CONFIG options during the
build. The .config is used just for storing the user's configuration.
I do not see a strong reason to use a particular pattern of comment
for disabled options.
With this commit, Kconfig will output disable options in a more natural
form, "CONFIG_FOO=n".
Kconfig accepts both "# CONFIG_FOO is not set" and "CONFIG_FOO=n" as a
valid input. You do not need to update arch/*/configs/*_defconfig files
for now. "git bisect" should be able to cross the commit in both ways
without any issue.
A problem may occur if you parse the .config for the "# ... is not set"
patterns.
I adjusted streamline_config.pl, merge_config.sh,
scripts/kconfig/tests/.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Reviewed-by: Boris Kolpackov <boris@codesynthesis.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
Signed-off-by: Yann CARDAILLAC <ycnakajsph@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
|
|
With EXPERT, EMBEDDED and DEBUG_KERNEL removed from the base, this
is no longer being selected by default in in standard BSPs, causing
breakage in things that relied on it.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The only users were the mips machines, which don't use it any more,
and it doesn't really make sense to completely disable ftrace anyway
(just don't enable it if you don't want it).
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This turns off CONFIG_FUNCTION_TRACER, CONFIG_FUNCTION_GRAPH_TRACER,
and CONFIG_DYNAMIC_FTRACE, which can cause problems on some
architectures such as mips
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add support for generic syscall entry/exit tracing.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Roughly corresponds to:
commit db575247e16e50ce5160e18907e253c6a43b6feb
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Mon Apr 4 00:27:55 2011 -0400
yocto: 2.6.39 baseline
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
...in the full history repo, but with some extraneous files that were
deleted post db575247 deleted right here and now at the baseline
instead.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
Bruce Ashfield
Yann CARDAILLAC
California Sullivan
Tom Zanussi
Bruce Ashfield
Tom Zanussi
Paul Gortmaker