public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Borislav Petkov <petkov@math.uni-muenster.de>,
	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 22:21:14 +0200	[thread overview]
Message-ID: <200610232221.14265.mb@bu3sch.de> (raw)
In-Reply-To: <1161602705.19388.22.camel@localhost.localdomain>

On Monday 23 October 2006 13:25, Alan Cox wrote:
> Ar Sad, 2006-10-21 am 10:17 +0200, ysgrifennodd Borislav Petkov:
> > This one should be probably made dependent on some #define saying that the cpu
> > is an AMD and has the LX Geode crypto hardware built in. Turn it off for now.
> 
> That makes no real sense. Most kernel selections are "run on lots of
> processor types", we thus want as much as possible modular, built and
> available.
> 
> The existing defaults seem quite sane.

I can only second that.
Building it as a module does not hurt, except few k disk space.
But that does not really hurt, given today's disk sizes. ;)
And if you have a small disk, you can still disable it.

-- 
Greetings Michael.

  parent reply	other threads:[~2006-10-23 20:22 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
2006-10-23 20:21   ` Michael Buesch [this message]
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=200610232221.14265.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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