All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 20 Jun 2001 10:26:58 +0200	[thread overview]
Message-ID: <20010620102658.A970@suse.cz> (raw)
In-Reply-To: <20010619193326.A295@suse.cz> <24417.992989367@ocs3.ocs-net>
In-Reply-To: <24417.992989367@ocs3.ocs-net>; from kaos@ocs.com.au on Wed, Jun 20, 2001 at 08:22:47AM +1000

On Wed, Jun 20, 2001 at 08:22:47AM +1000, Keith Owens wrote:

> On Tue, 19 Jun 2001 19:33:26 +0200, 
> Vojtech Pavlik <vojtech@suse.cz> wrote:
> >On Wed, Jun 20, 2001 at 12:43:02AM +1000, Keith Owens wrote:
> >> drivers/char/Makefile says
> >> subdir-$(CONFIG_INPUT) += joystick
> >
> >Ouch. Forgot about this one. I guess it'd be better to fix this, because
> >the gameport code really is independent on input.
> 
> The number of gameport devices is large enough to justify their own
> subdirectory, drivers/char/gameport instead of being lumped in with the
> joysticks.  What do you think?

Except that they're not character devices at all, I'm fine with this.

-- 
Vojtech Pavlik
SuSE Labs

      reply	other threads:[~2001-06-20  8:58 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
2001-06-19 22:22         ` Keith Owens
2001-06-20  8:26           ` Vojtech Pavlik [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=20010620102658.A970@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.