From: Josh Triplett <josh@joshtriplett.org>
To: Konrad Vrba <konrad.vrba@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: very strange dependencies on CONFIG_EXPERT=n in kernel 3.8
Date: Mon, 11 Mar 2013 11:49:17 -0700 [thread overview]
Message-ID: <20130311184916.GA6185@jtriplet-mobl1> (raw)
In-Reply-To: <CAF2Nc0zT5t_YeqzJWprUH7ma3_3LCWVXgbxLBODU7drgauDt=Q@mail.gmail.com>
On Sun, Mar 10, 2013 at 04:14:27PM +0100, Konrad Vrba wrote:
> Dear list,
> I have noticed that CONFIG_EXPERT=n makes the following options in the
> kernel required (unremovable):
>
> CONFIG_FW_LOADER=y
> CONFIG_EXTRA_FIRMWARE=""
> CONFIG_MOUSE_PS2_ALPS=y
> CONFIG_MOUSE_PS2_LOGIPS2PP=y
> CONFIG_MOUSE_PS2_SYNAPTICS=y
> CONFIG_MOUSE_PS2_LIFEBOOK=y
> CONFIG_MOUSE_PS2_TRACKPOINT=y
> CONFIG_VGA_ARB=y
> CONFIG_VGA_ARB_MAX_GPUS=16
> CONFIG_I8253_LOCK=y
> CONFIG_DEBUG_MEMORY_INIT=y
> CONFIG_PCSPKR_PLATFORM=y
>
> If I select CONFIG_EXPERT=y then I can remove those, but that creates
> a new problem by making CONFIG_DEBUG_KERNEL=y unremovable.
>
> To make a specific example, this makes it impossible to compile a kernel with
> CONFIG_FW_LOADER=n
> CONFIG_DEBUG_KERNEL=n
> at the same time
CONFIG_DEBUG_KERNEL, like CONFIG_EXPERT, should not directly affect the
code included in the kernel; it should just avoid asking about a pile of
other debugging options. In practice, a small amount of
architecture-specific code (for powerpc, parisc, and blackfin) did use
it as a generic debug option, but that needs fixing. So, for now, turn
on CONFIG_EXPERT and live with having CONFIG_DEBUG_KERNEL turned on.
That aside, several of the above options should not depend on EXPERT;
why would PCSPKR_PLATFORM or DEBUG_MEMORY_INIT need to depend on EXPERT?
- Josh Triplett
next prev parent reply other threads:[~2013-03-11 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 15:14 Konrad Vrba
2013-03-11 18:49 ` Josh Triplett [this message]
2013-03-12 14:52 ` Konrad Vrba
2013-03-12 16:39 ` 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=20130311184916.GA6185@jtriplet-mobl1 \
--to=josh@joshtriplett.org \
--cc=konrad.vrba@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®