On Mon, 24 Apr 2017 21:51:25 +0200, Michal Marek wrote:
Dne 24.4.2017 v 17:44 Takashi Iwai napsal(a):
BTW, recently I noticed that config/i386/default varies unstably after running run_oldconfig.sh. Some configs are turned on once, and turned off at the next update, or so. Any side-effect by this change...?
Do you remember what command you used to change the configs in
9add1483339d ("Enable CONFIG_KXCJK1013 for Cherrytrail devices (boo#1034809).")
IIRC, I just ran the usual patches/script/run_oldconfig.sh on the tree expanded by sequence-patch.
The logic for run_oldconfig.sh -nco-{y,m,n} is as follows:
# do not change trimmed configs unless requested if test -z "$set_flavor" && ! \ grep -q '^CONFIG_MMU=' "${prefix}config/$config"; then continue fi
Which means that if you explicitly specify the flavor, it will change even fragmented configs. This makes perfect sense for --flavor vanilla, but --flavor default is probably not explicit enough. That the option disappeared when Jeff ran run_oldconfig.sh is correct, because it was redundant.
I didn't specify the flavor. Or maybe I ran run_oldconfig.sh multiple times. That makes any difference? Takashi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org