From: Ingo Molnar <mingo@kernel.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Michal Hocko <mhocko@suse.cz>,
Vladimir Davydov <vdavydov@parallels.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andy Lutomirski <luto@amacapital.net>,
Bertrand Jacquin <beber@meleeweb.net>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Iulia Manda <iulia.manda21@gmail.com>,
Pranith Kumar <bobby.prani@gmail.com>,
Clark Williams <clark.williams@gmail.com>,
Mel Gorman <mgorman@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init/Kconfig: Fix break in middle of EXPERT menu
Date: Tue, 12 May 2015 09:04:55 +0200 [thread overview]
Message-ID: <20150512070455.GB30476@gmail.com> (raw)
In-Reply-To: <20150511181327.GA1884@jtriplet-mobl1>
* Josh Triplett <josh@joshtriplett.org> 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 <josh@joshtriplett.org>
> ---
>
> 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
next prev parent reply other threads:[~2015-05-12 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 18:13 [PATCH] init/Kconfig: Fix break in middle of EXPERT menu Josh Triplett
2015-05-11 18:23 ` Randy Dunlap
2015-05-11 20:23 ` [PATCH 2/1] init/Kconfig: Split expert menu into a separate file, init/Kconfig.expert Josh Triplett
2015-05-11 21:01 ` Paul Bolle
2015-05-11 21:18 ` Josh Triplett
2015-05-11 21:32 ` Paul Bolle
2015-05-11 21:47 ` Josh Triplett
2015-05-11 22:01 ` Paul Bolle
2015-05-11 22:40 ` Josh Triplett
2015-05-11 21:50 ` Paul Bolle
2015-05-11 22:04 ` Josh Triplett
2015-05-11 22:15 ` Paul Bolle
2015-05-28 8:13 ` Paul Bolle
2015-05-11 22:36 ` Luis R. Rodriguez
2015-05-11 22:51 ` Josh Triplett
2015-05-12 7:04 ` Ingo Molnar [this message]
2015-05-12 7:08 ` [PATCH] init/Kconfig: Fix break in middle of EXPERT menu Josh Triplett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150512070455.GB30476@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=beber@meleeweb.net \
--cc=bobby.prani@gmail.com \
--cc=clark.williams@gmail.com \
--cc=geert@linux-m68k.org \
--cc=hannes@cmpxchg.org \
--cc=iulia.manda21@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=paulmck@linux.vnet.ibm.com \
--cc=vdavydov@parallels.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox