From: Keith Owens <kaos@ocs.com.au>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: crc32 cleanups
Date: Sat, 13 Oct 2001 20:25:31 +1000 [thread overview]
Message-ID: <16790.1002968731@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "13 Oct 2001 12:02:16 +0200." <k2het3luxj.fsf@zero.aec.at>
On 13 Oct 2001 12:02:16 +0200,
Andi Kleen <ak@muc.de> wrote:
>Just use the existing linker features. Link the crc code as an .a library.
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.
>[Note that __initcall may be a bit tricky here if some other __initcall
>user like an ethernet driver needs crc32 too; there is unfortunately no
>priority mechanism in __initcall to enforce that the crc32 init runs before
>the other initcalls. best would probably just to use a static table to avoid
>this issue]
???! __initcall entries are executed in the order that they are linked
into the kernel. The linkage order is controlled by the order that
Makefiles are processed during kbuild and by line order within each
Makefile. There is definitely a priority order for __initcall code.
next prev parent reply other threads:[~2001-10-13 10:25 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
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 [this message]
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=16790.1002968731@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=ak@muc.de \
--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
all inboxes | Powered by JetHome®