public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "gguevel" <gguevel@interfaceconcept•com>
To: <linuxppc-embedded@lists•linuxppc.org>
Subject: Problem with module installation under 2.4.x kernel
Date: Tue, 15 Oct 2002 18:25:11 +0200	[thread overview]
Message-ID: <000001c27467$6fd3cc00$3101a8c0@DOMAIN> (raw)


I worked under Linux 2.2.x Kernel and I have no problem with the module
generation.

Now under Linux 2.4.x Kernel, I can compile modules and install them but
I have the following warning while running "insmod xxxx"
Warning: loading xxxx will taint the kernel: no license.

Does anyone know what I must add to my module to avoid this warning ?

Thanks
Gérard


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-10-15 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 16:25 gguevel [this message]
2002-10-15 16:58 ` Problem with module installation under 2.4.x kernel Kurt Wall
2002-10-15 18:01   ` Image Download Aman
  -- strict thread matches above, loose matches on Subject: below --
2002-10-15 16:31 Problem with module installation under 2.4.x kernel erik.teose

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='000001c27467$6fd3cc00$3101a8c0@DOMAIN' \
    --to=gguevel@interfaceconcept$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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