[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A8E78D.1040809@garzik.org>
Date: Thu, 26 Jul 2007 14:27:25 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: david@...g.hm, Len Brown <lenb@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-acpi@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] ACPI patches for 2.6.23-rc1
Linus Torvalds wrote:
>
> On Thu, 26 Jul 2007, david@...g.hm wrote:
>> how about the fact that Linus found the problem becouse his system didn't work
>> right?
>
> No, it works, it just forces me to use a configuration that I'm not
> personally interested in on that particular machine.
>
> I tend to like using minimal kernels. I don't use modules on most of my
> machines, and I actually look over my config. Maybe I'm odd. But I think
> it's a good thing to let people decide what they want (and what they do
> _not_ want) in their kernels.
>
> I think forcing people to use CPU_HOTPLUG is a mistake. There's a reason
> that existed as a config option. The ACPI changes basically mean that the
> whole CPU_HOTPLUG config option is totally pointless, because everybody is
> forced to have it.
Indeed -- forced to have a feature that is applicable in reality to
0.00000001% of the user population, I'd wager :)
I read and hone my .config to utter minimalist perfection too :) So
count my vote here too, for -not- wanting CPU_HOTPLUG dead code in my
kernel.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists