From: Mike Galbraith <efault@gmx.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sunil Naidu <akula2.shark@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: menuconfig issue (checklist) in 2.6.20.7 & 2.6.21-rc7 ?
Date: Fri, 27 Apr 2007 08:03:42 +0200 [thread overview]
Message-ID: <1177653822.25885.25.camel@Homer.simpson.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0704270739510.506@yvahk01.tjqt.qr>
On Fri, 2007-04-27 at 07:40 +0200, Jan Engelhardt wrote:
> On Apr 26 2007 05:06, Mike Galbraith wrote:
> >On Wed, 2007-04-25 at 22:30 +0200, Sam Ravnborg wrote:
> >
> >> > There are general funnies in the menuconfig world (my preference) here.
> >> > For instance, I recently had reason to change/test different default IO
> >> > schedulers, and found that no matter what I did, I couldn't select a
> >> > default IO scheduler any more, though I used to be able to do so.
> >
> >> Tried it now with latest -git from Linus and here it works.
> >> Notice that you need to make the scheduler a built-in <*>
> >> before you can select it as default.
> >> A scheduler selected as a module <M> cannot be made default.
> >
> >Ok, I guess my ncurses is ill. (all built in) Thanks.
>
> CONFIG_MODULES=n?
No, I have more modules that you can shake a stick at.
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODULE_SRCVERSION_ALL=y
-Mike
next prev parent reply other threads:[~2007-04-27 6:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 14:24 Sunil Naidu
2007-04-25 14:35 ` Dan Kruchinin
2007-04-25 14:36 ` Michael Tokarev
2007-04-25 22:51 ` Sunil Naidu
2007-04-25 19:07 ` Andrew Morton
2007-04-25 19:31 ` Mike Galbraith
2007-04-25 20:30 ` Sam Ravnborg
2007-04-26 3:06 ` Mike Galbraith
2007-04-27 5:40 ` Jan Engelhardt
2007-04-27 6:03 ` Mike Galbraith [this message]
2007-04-27 17:17 ` Randy Dunlap
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=1177653822.25885.25.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=akula2.shark@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®