public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olivier Smeesters <smeesters@octalis.com>
To: linux-kernel@vger.kernel.org
Cc: smeesters@octalis.com
Subject: compiling two modules from separate directories out of kernel tree
Date: Fri, 18 Feb 2005 15:33:31 +0100	[thread overview]
Message-ID: <4215FCBB.6030906@octalis.com> (raw)

Dear all,

I'm currently developping two kernel modules that I'm compiling outside 
of the kernel tree. One is a device driver and one is a pseudo-network 
device driver (encapsulating network packets).
The output of the encapsulator is supposed to go to the device driver. 
For this reason, the device driver exports a "send_packet" function 
which the encapsulator calls.

When loading the encapsulator module, the kernel reports a 'no version 
for "send_packet" found' and goes in tainted mode.
It seems that this is caused by the fact that the two modules are 
compiled in different directories (there is no CRC for the send_packet 
function in the encapsulator module, only for the kernel functions it 
calls).

One solution is to put all the modules in one directory. When this is 
done, a CRC is present in the encapsulator module as expected by the 
module loader and there is no warning anymore.
But as the two drivers are not definitely related (the device driver can 
be used without the encapsulator), I would like to keep them in separate 
directories.
This situation ressembles to the situation of the PLIP and the parport 
driver.

Is there a way to avoid the warning (and tainted mode) while still 
compiling them outside of the kernel tree and in separate directories ?

Thanks in advance,


Olivier Smeesters


                 reply	other threads:[~2005-02-18 14:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4215FCBB.6030906@octalis.com \
    --to=smeesters@octalis.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