From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Andreas Mohr <andi@lisas.de>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Vojtech Pavlik <vojtech@suse.cz>, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 1/2] SOUND: kill gameport bits
Date: Wed, 20 Aug 2014 13:29:02 +0100 [thread overview]
Message-ID: <20140820132902.7eed767f@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <s5htx57hc89.wl-tiwai@suse.de>
> It's the gameport core code that is currently broken under some
> situation, right? If so, marking it as broken is the first step, and
> we don't need to touch else. We may fix it later, or we may not. If
> the thing isn't improved, then we can drop the whole stuff.
It's only broken on x86 with frequency changing. x86 is not the only
platform with ISA or PCI bus or gameports.
It really ought to go via staging, and the other arch maintainers be
asked. The m68k and mips world does include a department of relics and
retro-computing 8)
I suspect nobody cares however.
Alan
next prev parent reply other threads:[~2014-08-20 12:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 2:46 [PATCH 1/2] SOUND: kill gameport bits Andreas Mohr
2014-08-20 5:18 ` Dmitry Torokhov
2014-08-20 5:50 ` Andreas Mohr
2014-08-20 6:09 ` Takashi Iwai
2014-08-20 6:31 ` Dmitry Torokhov
2014-08-20 7:05 ` Takashi Iwai
2014-08-20 12:15 ` Takashi Iwai
2014-08-20 14:49 ` Dmitry Torokhov
2014-08-21 7:16 ` Geert Uytterhoeven
2014-08-20 12:29 ` One Thousand Gnomes [this message]
2014-08-20 12:53 ` Geert Uytterhoeven
2014-08-21 11:29 ` Takashi Iwai
2014-08-24 5:07 ` Andreas Mohr
2014-08-25 7:13 ` Takashi Iwai
2014-08-28 20:03 ` Clemens Ladisch
2014-08-28 21:11 ` Vojtech Pavlik
2014-08-20 14:27 ` Andreas Mohr
2014-08-20 14:48 ` Dmitry Torokhov
2014-08-20 6:39 ` Vojtech Pavlik
2014-08-20 12:20 ` One Thousand Gnomes
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 16:41 Dmitry Torokhov
2014-08-20 7:33 ` Clemens Ladisch
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=20140820132902.7eed767f@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=andi@lisas.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=vojtech@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).