From: Keith Owens <kaos@ocs.com.au>
To: Stephen Wille Padnos <stephenwp@adelphia.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Exporting new functions from kernel 2.2.14
Date: Wed, 06 Jun 2001 00:22:57 +1000 [thread overview]
Message-ID: <17882.991750977@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 05 Jun 2001 10:10:26 MST." <3B1D1282.9D74F4AF@adelphia.net>
On Tue, 05 Jun 2001 10:10:26 -0700,
Stephen Wille Padnos <stephenwp@adelphia.net> wrote:
>Arthur had pointed out that modules.h should be included, then kernel.h. Is
>there a place where I can find out more about header file order dependencies?
With the existing design for module symbol versions, module.h must
appear before other headers, to obtain the mapping of normal symbols to
hashed symbols. That restriction will be removed in 2.5, when the
broken Makefile design for module versions is replaced.
prev parent reply other threads:[~2001-06-05 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 15:54 Exporting new functions from kernel 2.2.14 Stephen Wille Padnos
2001-06-05 13:10 ` Arthur Naseef
2001-06-05 13:24 ` Keith Owens
2001-06-05 13:25 ` Arthur Naseef
2001-06-05 17:09 ` Stephen Wille Padnos
2001-06-05 17:32 ` Stephen Wille Padnos
2001-06-05 14:59 ` Keith Owens
2001-06-05 13:23 ` Keith Owens
2001-06-05 17:10 ` Stephen Wille Padnos
2001-06-05 14:22 ` Keith Owens [this message]
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=17882.991750977@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=stephenwp@adelphia.net \
/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