public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: petkov@math.uni-muenster.de
Cc: Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	info-linux@geode.amd.com
Subject: Re: [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default
Date: Mon, 23 Oct 2006 18:35:34 +0100	[thread overview]
Message-ID: <1161624935.21701.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20061023170931.GB21995@gollum.tnic>

Ar Llu, 2006-10-23 am 19:09 +0200, ysgrifennodd Borislav Petkov:
> ... should the duration of the the kernel compilation be prolonged then by 
> unneeded modules? Does the majority of people really use that crypto hardware or
> is it a small percentage only, we don't know but it also doesn't seem pretty sensible to do
> 'make oldconfig' and go and turn off all modules that I don't need/have by hand;
> it gets quite annoying sometimes too.

Every person has a unique and individual definitionof "un-needed
module". In addition developers want more to be compiled as it helps
catch errors earlier. Thus there are reasons for things defaulting to
"on" a lot of the time.

Also bear in mind that you can copy ".config" files between releases and
make oldconfig quite easily so you only have to turn it off once. 

It would be far more productive IMHO to write a tool which generates
a .config file by inspecting the kernel source and the machine upon
which the script is run. This could use the extracted pci data tables in
the modules to produce a correct minimal kernel for many systems.

Alan


  reply	other threads:[~2006-10-23 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21  8:17 [PATCH] do not compile AMD Geode's hwcrypto driver as a module per default Borislav Petkov
2006-10-23 11:25 ` Alan Cox
2006-10-23 12:20   ` Borislav Petkov
2006-10-23 17:09   ` Borislav Petkov
2006-10-23 17:35     ` Alan Cox [this message]
2006-10-23 20:21   ` Michael Buesch
2006-10-24  5:49     ` 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=1161624935.21701.14.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=info-linux@geode.amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petkov@math.uni-muenster.de \
    /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