public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Wille Padnos <stephenwp@adelphia.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Exporting new functions from kernel 2.2.14
Date: Tue, 05 Jun 2001 10:09:02 -0700	[thread overview]
Message-ID: <3B1D122E.87AEF85F@adelphia.net> (raw)
In-Reply-To: <OIBBKHIAILDFLNOGGFMNOEHLCBAA.arthur.naseef@ariel.com>

Thanks.

Actually, the symbols in question aren't in modules.  The kernel is module
enabled, but all drivers are being compiled in (this is for an embedded
system).  My external module (which needs to grab the timer interrupt) is in a
separate source tree.

Thanks for the printk info - I guess boneheads like me could use a FAQ that
tells which order the miscellaneoud include files need to be in.  (I had
modules.h after linux.h).  I changed the order, butI am waiting for a recompile
now, so I don't know if the reordering worked.

Arthur Naseef wrote:

...

> you can edit the .ver file yourself (under /usr/src/linux/include/modules/)
> and add entries.  This will eliminate the funny versioning, as in:
> As far as the printk() warning, you need to make sure your module code
> includes the right header files.  In this case, I believe you need to grab
> <linux/kernel.h> after including <linux/module.h>.
>
> I hope this helps.
>
> -art
>




  parent reply	other threads:[~2001-06-05 14:08 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 [this message]
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

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=3B1D122E.87AEF85F@adelphia.net \
    --to=stephenwp@adelphia.net \
    --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