From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>, linux-kernel@vger.kernel.org
Subject: Re: crc32 cleanups
Date: Sat, 13 Oct 2001 13:12:17 +1000 [thread overview]
Message-ID: <15369.1002942737@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 12 Oct 2001 21:56:42 EST." <Pine.LNX.3.96.1011012215110.20962C-100000@mandrakesoft.mandrakesoft.com>
On Fri, 12 Oct 2001 21:56:42 -0500 (CDT),
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>The easy solution to all this is obviously to build crc32 into the
>kernel unconditionally, and live with the kernel bloat. I don't like
>kernel bloat, so I prefer the non-easy option.
Not when your non-easy option requires every driver that needs a
library routine to patch lib/Makefile. Adding a new driver should not
require a patch to an unrelated area of the kernel, it is bad design.
It also results on overlapping patches with the attendent risk of patch
rejects. Anybody remember the common Space.c and all the problems that
file caused?
Kernel bloat is bad. A kbuild design that will cause maintainence
problems in future is even worse. Setting CONFIG_CRC32 at the time the
driver is selected is the cleanest solution.
next prev parent reply other threads:[~2001-10-13 3:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 19:11 Matt Domsch
2001-10-12 19:25 ` Jeff Garzik
2001-10-12 19:37 ` Jeff Garzik
2001-10-13 1:51 ` Keith Owens
2001-10-13 2:36 ` Jeff Garzik
2001-10-13 2:45 ` Keith Owens
2001-10-13 2:56 ` Jeff Garzik
2001-10-13 3:12 ` Keith Owens [this message]
2001-10-12 19:45 ` Horst von Brand
2001-10-12 20:07 ` Jeff Garzik
2001-10-13 1:04 ` Horst von Brand
2001-10-13 1:09 ` Jeff Garzik
2001-10-13 12:45 ` Horst von Brand
2001-10-13 9:48 ` Jan-Marek Glogowski
2001-10-13 10:02 ` Andi Kleen
2001-10-13 10:07 ` Jan-Marek Glogowski
2001-10-13 23:09 ` Horst von Brand
2001-10-13 10:25 ` Keith Owens
2001-10-15 8:29 ` Bjorn Wesen
2001-10-15 11:35 ` Keith Owens
2001-10-12 20:17 Matt_Domsch
2001-10-12 20:34 ` Jeff Garzik
2001-10-13 1:20 ` Horst von Brand
2001-10-13 15:16 ` Martin Dalecki
2001-10-13 1:09 ` Horst von Brand
2001-10-13 1:20 ` Jeff Garzik
2001-10-12 22:20 Matt_Domsch
2001-10-12 22:34 ` Jeff Garzik
2001-10-13 2:09 Stuart Lynne
2001-10-13 3:46 Matt_Domsch
2001-10-13 11:47 ` Kai Henningsen
2001-10-14 3:19 Matt_Domsch
2001-10-15 11:34 Samium Gromoff
2001-10-16 19:05 Matt_Domsch
2001-10-23 21:19 Matt_Domsch
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=15369.1002942737@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=Matt_Domsch@dell.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome