From: Borislav Petkov <borislav.petkov@amd.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
dougthompson@xmission.com
Subject: Re: linux-next: Tree for May 20 (amd64_edac)
Date: Wed, 20 May 2009 19:17:54 +0200 [thread overview]
Message-ID: <20090520171754.GB29913@aftab> (raw)
In-Reply-To: <4A14352C.5020508@oracle.com>
Hi,
On Wed, May 20, 2009 at 09:51:56AM -0700, Randy Dunlap wrote:
[..]
> Distros don't use defaults or defconfig anyway, and having them
> enabled bloats kernels. I'm sure that Linus has also expressed
> opinions about enabling options in this way, but I can't find it
> just now.
This is one of those situations where you have the pros and the cons
staring at you. For what is worth, I myself have sent several patches
removing Kconfig options defaulting to m for hardware which is not even
present on a two-digit percentage of machines. I was told then, that it
is defaulting to m so that the code sees some more compiles on different
hardware but we end up automating stuff to turn them off in the .config
and the whole thing doesn't serve its purpose in the end anyway.
Besides, those who enable EDAC should probably know what they need to
turn on, in addition to that. Also, the bloating part is not good(tm).
So off it is...
--
Regards/Gruss,
Boris.
Operating | Advanced Micro Devices GmbH
System | Karl-Hammerschmidt-Str. 34, 85609 Dornach b. München, Germany
Research | Geschäftsführer: Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
(OSRC) | Registergericht München, HRB Nr. 43632
prev parent reply other threads:[~2009-05-20 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 7:08 linux-next: Tree for May 20 Stephen Rothwell
2009-05-20 16:16 ` linux-next: Tree for May 20 (amd64_edac) Randy Dunlap
2009-05-20 16:41 ` Borislav Petkov
2009-05-20 16:51 ` Randy Dunlap
2009-05-20 17:17 ` Borislav Petkov [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=20090520171754.GB29913@aftab \
--to=borislav.petkov@amd.com \
--cc=dougthompson@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).