From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Arun Prasad <arun@netlab.hcltech.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.51 CRC32 undefined
Date: 07 Mar 2003 15:59:01 +0000 [thread overview]
Message-ID: <1047052741.32200.82.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303070749160.2876-100000@home.transmeta.com>
On Fri, 2003-03-07 at 15:49, Linus Torvalds wrote:
> I don't want to have configs like this. I personally refuse to load
> modules into my kernel, and as such a subsystem that only works as a
> module is _evil_.
It works built-in and would continue to do so with this patch applied.
It's built into your kernel _automatically_ if anything built-in
requires it. That's done by the makefiles. Likewise, it's built as a
module automatically if anything modular in your tree requires it.
The config option is _only_ relevant if you are explicitly adding crc32
in the knowledge that you're going to build an _external_ module which
requires it.
However, setting the config option to 'Y' when you have only _modular_
stuff which requires it is broken because it doesn't actually get pulled
in from lib/lib.a, because nothing references it.
--
dwmw2
next prev parent reply other threads:[~2003-03-07 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 13:22 2.5.51 CRC32 undefined Arun Prasad
2003-03-07 12:40 ` David Woodhouse
2003-03-07 15:27 ` Kai Germaschewski
2003-03-07 15:43 ` Jeff Garzik
2003-03-10 13:14 ` =?unknown-8bit?Q?J=F6rn?= Engel
2003-03-07 15:49 ` Linus Torvalds
2003-03-07 15:59 ` David Woodhouse [this message]
2003-03-07 16:10 ` Jeff Garzik
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=1047052741.32200.82.camel@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=arun@netlab.hcltech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).