From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752900AbbELHFD (ORCPT ); Tue, 12 May 2015 03:05:03 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:36143 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752673AbbELHFA (ORCPT ); Tue, 12 May 2015 03:05:00 -0400 Date: Tue, 12 May 2015 09:04:55 +0200 From: Ingo Molnar To: Josh Triplett Cc: Andrew Morton , "Paul E. McKenney" , Michal Hocko , Vladimir Davydov , Johannes Weiner , Geert Uytterhoeven , Andy Lutomirski , Bertrand Jacquin , "Luis R. Rodriguez" , Iulia Manda , Pranith Kumar , Clark Williams , Mel Gorman , linux-kernel@vger.kernel.org Subject: Re: [PATCH] init/Kconfig: Fix break in middle of EXPERT menu Message-ID: <20150512070455.GB30476@gmail.com> References: <20150511181327.GA1884@jtriplet-mobl1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150511181327.GA1884@jtriplet-mobl1> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Josh Triplett wrote: > Commit e1abf2cc8d5 ("bpf: Fix the build on BPF_SYSCALL=y && > !CONFIG_TRACING kernels, make it more configurable") made BPF_SYSCALL no > longer hidden with !EXPERT, but left it in the middle of the EXPERT > menu. menuconfig stops putting config items under a submenu once it > encounters an item that doesn't depend on the menu's config item, so > this caused the remainder of the EXPERT menu to spill out into the > containing menu around it. Fix by moving BPF_SYSCALL before the EXPERT > menu, next to BPF. > > Fixes: e1abf2cc8d5 ("bpf: Fix the build on BPF_SYSCALL=y && !CONFIG_TRACING kernels, make it more configurable") > Signed-off-by: Josh Triplett > --- > > Ingo, do you want to take this through -tip? Or should this go > through some other tree? I can pick it up, but -mm might be better suited for this, if you do: > I'm also thinking about splitting the entire EXPERT menu into a > separate Kconfig.expert and including it from init/Kconfig, to make > it clear that everything in that menu should only be visible if > EXPERT. Right now, the long EXPERT menu blends into the longer > init/Kconfig, and issues like this happen every few kernel releases. That's a good idea as well. Thanks, Ingo