mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: "Cédric Augonnet" <cedric.augonnet@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: input_polldev won't load as a module
Date: Sat, 26 May 2007 23:42:37 -0400	[thread overview]
Message-ID: <200705262342.37768.dtor@insightbb.com> (raw)
In-Reply-To: <f56c1ba00705261425t1e6eb59as72ca5f6e3a3c4d0@mail.gmail.com>

Hi Cédric,

On Saturday 26 May 2007 17:25, Cédric Augonnet wrote:
> Hi,
> 
> When trying to load input_polldev compiled as a module on my
> 2.6.22-rc2-mm1 kernel, it is impossible because of some symbols that
> are said to be missing :
> 
> gonnet@porcinet:~$ sudo modprobe input_polldev
> FATAL: Error inserting input_polldev
> (/lib/modules/2.6.22-rc2-mm1=porcinet/kernel/drivers/input/misc/input-polldev.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> gonnet@porcinet:~$ dmesg
> [  137.559553] input_polldev: Unknown symbol queue_delayed_work
> [  137.559621] input_polldev: Unknown symbol destroy_workqueue
> [  137.559652] input_polldev: Unknown symbol __create_workqueue
> 
> I enclosed my .config in case it may help.
> 
> On the other hand, if I choose CONFIG_INPUT_POLLDEV=y, it seems to
> work without any problem. Provided the Kconfig file, it looks like
> this could compiled either like that or as a module.
> 
> Unfortunately, given my very limited understanding i could really not
> figure out why these symbols cannot be resolved, so i'll be really
> interrested if anyone can propose a solution or an explanation.
> 

It is caused by nyssing GPL license for the module. Please try 2.6.22-rc3,
the issue should be fixed by commit 36bd52a49b790a71f3d353cdddf2f22e1e6f84ff.

-- 
Dmitry

      reply	other threads:[~2007-05-27  3:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 21:25 Cédric Augonnet
2007-05-27  3:42 ` Dmitry Torokhov [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=200705262342.37768.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=cedric.augonnet@gmail.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

Powered by JetHome