From: Samium Gromoff <_deepfire@mail.ru>
Message-Id: <200110151134.f9FBYkS00992@vegae.deep.net>
Subject: Re: crc32 cleanups
To: bjorn@sparta.lu.se
Date: Mon, 15 Oct 2001 15:34:45 +0400 (MSD)
Cc: linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

> > Does not work if all the code that uses crc32 is in a module.  No
> > references from the main kernel so crc32 is not included by the linker.
>
> So make the CRC32 code a module itself ?
   Nasty idea, since its ideologically unclean.
   The idea behind the CONFIG_xxx options is to give user the control over
 the kernel content in the cases he really can win from it.
   I suppose no sane user knows what crc32 is needed by, nor even whats it..   
   Nor he should, since maximum of his knowledge lies in device selection,
 which is the proper source for such information.

   What i`m trying to say is that CONFIG_xxx is just the wrong information
 bearer for that.

Cheers, Samium Gromoff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/