mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <petkov@uni-muenster.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: "Brown, Len" <len.brown@intel.com>, Andi Kleen <ak@suse.de>,
	akpm@osdl.org, acpi-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.6.13-mm2] set IBM ThinkPad extras to default n in Kconfig
Date: Sat, 10 Sep 2005 11:42:59 +0200	[thread overview]
Message-ID: <20050910094259.GA16051@gollum.tnic> (raw)
In-Reply-To: <Pine.LNX.4.61.0509091817220.3743@scrub.home>

On Fri, Sep 09, 2005 at 06:25:00PM +0200, Roman Zippel wrote:
 
> The best would be to avoid using defaults completely, unless the resulting 
> kernel is non-functional (e.g. it doesn't compile or boot).
> So far it's still the responsibility of the user to explicitly turn 
> everything on he needs (at least until we have a functional autoconfig).
> BTW distros are not the only users, from them I would expect how to 
> configure a kernel.

Actually, this sounds pretty sane and IMHO is somehow the biggest common
denominator concerning linux users and their kernel configuration
recreational activities :); but seriously, going all over the menus of Kbuild
and turning everything off is a lot of work compared to turning on the
several things I need on my system. "default m" is also not a good thing
since compiling of unnecessary modules is simply dumb for a system
that's just not going to use them.

Regards,
		Boris.

  reply	other threads:[~2005-09-10  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 16:06 Brown, Len
2005-09-09 16:25 ` Roman Zippel
2005-09-10  9:42   ` Borislav Petkov [this message]
2005-09-10  9:47     ` [ACPI] " Erik Slagter
2005-09-10 10:20     ` Andi Kleen
2005-09-09 16:29 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-09-09  7:53 Borislav Petkov

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=20050910094259.GA16051@gollum.tnic \
    --to=petkov@uni-muenster.de \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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®