From: Martin Dalecki <dalecki@evision-ventures.com>
To: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Matt_Domsch@Dell.com, linux-kernel@vger.kernel.org
Subject: Re: crc32 cleanups
Date: Sat, 13 Oct 2001 17:16:55 +0200 [thread overview]
Message-ID: <3BC85AE7.80D340C8@evision-ventures.com> (raw)
In-Reply-To: <200110130120.f9D1K2L0024119@sleipnir.valparaiso.cl>
Horst von Brand wrote:
>
> Jeff Garzik <jgarzik@mandrakesoft.com> said:
>
> [...]
>
> > I was pondering whether it was ok to unconditionally include the
> > lib/crc32.c code, regardless of need. I am leaning towards "no," which
> > implies Makefile and Config.in rules which must be updated for each
> > driver that uses crc32.
>
> It is easier in that case just to make it another module.
That will waste space due to page granularity.
next prev parent reply other threads:[~2001-10-13 15:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 20:17 crc32 cleanups Matt_Domsch
2001-10-12 20:34 ` Jeff Garzik
2001-10-13 1:20 ` Horst von Brand
2001-10-13 15:16 ` Martin Dalecki [this message]
2001-10-13 1:09 ` Horst von Brand
2001-10-13 1:20 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-10-23 21:19 Matt_Domsch
2001-10-16 19:05 Matt_Domsch
2001-10-15 11:34 Samium Gromoff
2001-10-14 3:19 Matt_Domsch
2001-10-13 3:46 Matt_Domsch
2001-10-13 11:47 ` Kai Henningsen
2001-10-13 2:09 Stuart Lynne
2001-10-12 22:20 Matt_Domsch
2001-10-12 22:34 ` Jeff Garzik
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
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
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=3BC85AE7.80D340C8@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Matt_Domsch@Dell.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@sleipnir.valparaiso.cl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.