public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dwight Engen <dwight.engen@oracle.com>,
	Eric Paris <eparis@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Jiri Slaby <jslaby@suse.cz>, Kyungsik Lee <kyungsik.lee@lge.com>,
	Michal Hocko <mhocko@suse.cz>, Michal Marek <mmarek@suse.cz>,
	Mike Frysinger <vapier@gentoo.org>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Rob Landley <rob@landley.net>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: Make allnoconfig disable options behind EMBEDDED and EXPERT
Date: Tue, 25 Feb 2014 17:45:03 -0800	[thread overview]
Message-ID: <20140226014502.GA6641@thin> (raw)
In-Reply-To: <20140225130925.813f29105079cbd3d5a9ba30@linux-foundation.org>

On Tue, Feb 25, 2014 at 01:09:25PM -0800, Andrew Morton wrote:
> On Sun, 23 Feb 2014 18:20:26 -0800 Josh Triplett <josh@joshtriplett.org> wrote:
> > "make allnoconfig" exists to ease testing of minimal configurations.
> > Documentation/SubmitChecklist includes a note to test with allnoconfig.
> > This helps catch missing dependencies on common-but-not-required
> > functionality, which might otherwise go unnoticed.
> > 
> > However, allnoconfig still leaves many symbols enabled, because they're
> > hidden behind CONFIG_EMBEDDED or CONFIG_EXPERT.  For instance,
> > allnoconfig still has CONFIG_PRINTK and CONFIG_BLOCK enabled, so drivers
> > don't typically get build-tested with those disabled.
> > 
> > To address this, introduce a new Kconfig option "allnoconfig_y", used on
> > symbols which only exist to hide other symbols.  Set it on
> > CONFIG_EMBEDDED (which then selects CONFIG_EXPERT).  allnoconfig will
> > then disable all the symbols hidden behind those.
> 
> Now look what you've done!
> 
> kernel/sched/core.c: In function 'pick_next_task':
> kernel/sched/core.c:2613: warning: control reaches end of non-void function

Hey, look, now allnoconfig turns off more of the more-rarely-disabled
options, and turns up bugs and warnings that most people don't see!
Yay! ;)

So, yes, we should go ahead and get BUG() fixed properly, at a minimum
by using __builtin_unreachable().  I'll send a patch for that, as a
followup to the thread where Arnd mentioned how to do so.

- Josh Triplett

      reply	other threads:[~2014-02-26  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  2:20 [PATCH] kconfig: Make allnoconfig disable options behind EMBEDDED and EXPERT Josh Triplett
2014-02-24 22:19 ` Paul E. McKenney
2014-02-25 21:09 ` Andrew Morton
2014-02-26  1:45   ` Josh Triplett [this message]

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=20140226014502.GA6641@thin \
    --to=josh@joshtriplett.org \
    --cc=akpm@linux-foundation.org \
    --cc=dwight.engen@oracle.com \
    --cc=eparis@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=kyungsik.lee@lge.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mmarek@suse.cz \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rob@landley.net \
    --cc=vapier@gentoo.org \
    --cc=yann.morin.1998@free.fr \
    /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