On Mon, 2013-06-24 at 14:41 +0300, Fathi Boudra wrote: > Hi, > > There's a few warning that nobody noticed or cared until now: > [...] > Value requested for CONFIG_OABI_COMPAT not in final .config > Requested value: # CONFIG_OABI_COMPAT is not set > Actual value: > > Value requested for CONFIG_MTD_CHAR not in final .config > Requested value: CONFIG_MTD_CHAR=y > Actual value: > > Value requested for CONFIG_ENABLE_DEFAULT_TRACERS not in final .config > Requested value: CONFIG_ENABLE_DEFAULT_TRACERS=y > Actual value: > [...] > > MTD_CHAR doesn't exist anymore. > ENABLE_DEFAULT_TRACERS depends on !GENERIC_TRACER
That option is the minimum required for Gator, but we now have more trace configs enabled which superced the minimal generic traces, so if they are staying, then we can drop the default trace option. > > Is there any objection to drop both options from linaro-base.conf? > I'm not sure what to do with OABI_COMPAT. I disabled that [1] because it was crashing our kernels when doing ARM builds, not sure what the current state of the kernel is. It's an obscure option and I can't imagine that many people actually have it enabled, so could well still be broken in the mainline kernel. Irrespective of whether it crashes, do we actually want to have support for non AEBI user side code? Also, from the help text "This option adds a tiny overhead to all syscalls and produces a slightly larger kernel." [1] https://git.linaro.org/gitweb?p=kernel/configs.git;a=commit;h=46164b8909c93dc64a4fccd0cf93e5327265a50d -- Tixy _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
