From: Dave Jones <davej@redhat.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Export symbols so CONFIG_INPUT works as a module
Date: Tue, 24 Jan 2006 13:34:32 -0500 [thread overview]
Message-ID: <20060124183432.GA27917@redhat.com> (raw)
In-Reply-To: <20060124181945.GA21955@deprecation.cyrius.com>
On Tue, Jan 24, 2006 at 06:19:45PM +0000, Martin Michlmayr wrote:
> Currently, modular input support fails to load with the following error:
>
> qube:# modprobe input
> input: Unknown symbol kobject_get_path
> input: Unknown symbol add_input_randomness
>
> In the short run, this can be solved by exporting these two symbols.
> There have been discussions about fixing this in a different manner,
> see http://www.ussg.iu.edu/hypermail/linux/kernel/0505.2/1068.html
> Since this was in the days of 2.6.12-rc4 and modular input support is
> still broken, I suggest these symbols to be exported for now.
Is there actually any practical reason why you would want to
make the input layer modular ?
Dave
next prev parent reply other threads:[~2006-01-24 18:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 18:19 [PATCH] Export symbols so CONFIG_INPUT works as a module Martin Michlmayr
2006-01-24 18:31 ` Arjan van de Ven
2006-01-24 18:34 ` Dave Jones [this message]
2006-01-24 18:41 ` Al Viro
2006-01-24 23:08 ` Dmitry Torokhov
2006-01-24 23:14 ` Martin Michlmayr
2006-01-25 5:04 ` Dmitry Torokhov
2006-01-25 7:51 ` Vojtech Pavlik
2006-01-25 10:54 ` Martin Michlmayr
2006-01-26 22:17 ` Adrian Bunk
2006-01-25 14:20 ` Jan Engelhardt
2006-02-03 22:36 ` [2.6 patch] make INPUT a bool Adrian Bunk
2006-01-24 19:08 ` [PATCH] Export symbols so CONFIG_INPUT works as a module Martin Michlmayr
2006-01-24 19:20 ` Dave Jones
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=20060124183432.GA27917@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tbm@cyrius.com \
/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