From: Vojtech Pavlik <vojtech@suse.cz>
To: Keith Owens <kaos@ocs.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.5-ac15 -- Unresolved symbols "gameport_register_port"
Date: Tue, 19 Jun 2001 19:33:26 +0200 [thread overview]
Message-ID: <20010619193326.A295@suse.cz> (raw)
In-Reply-To: <20010619163520.A12869@suse.cz> <20719.992961782@ocs3.ocs-net>
In-Reply-To: <20719.992961782@ocs3.ocs-net>; from kaos@ocs.com.au on Wed, Jun 20, 2001 at 12:43:02AM +1000
On Wed, Jun 20, 2001 at 12:43:02AM +1000, Keith Owens wrote:
> On Tue, 19 Jun 2001 16:35:20 +0200,
> Vojtech Pavlik <vojtech@suse.cz> wrote:
> >On Wed, Jun 20, 2001 at 12:30:05AM +1000, Keith Owens wrote:
> >> Gameports and joysticks should not be available unless input core
> >> support is selected first. Invalid configs were slipping through.
> >
> >Gameports are not input core dependent.
> >Only joysticks are.
>
> drivers/char/Makefile says
> subdir-$(CONFIG_INPUT) += joystick
>
> Gameports are in subdir joystick. Certainly looks dependent on
> CONFIG_INPUT to me.
Ouch. Forgot about this one. I guess it'd be better to fix this, because
the gameport code really is independent on input.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-06-19 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 12:48 2.4.5-ac15 -- Unresolved symbols "gameport_register_port" and "gameport_unregister_port" in char/joystick/[cs461x.o, emu10k1-gp.o, lightning.o, ns558.o, pcigame.o] (fwd) axel
2001-06-19 14:30 ` 2.4.5-ac15 -- Unresolved symbols "gameport_register_port" Keith Owens
2001-06-19 14:35 ` Vojtech Pavlik
2001-06-19 14:43 ` Keith Owens
2001-06-19 17:33 ` Vojtech Pavlik [this message]
2001-06-19 22:22 ` Keith Owens
2001-06-20 8:26 ` Vojtech Pavlik
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=20010619193326.A295@suse.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.