From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Borislav Petkov <petkov@uni-muenster.de>,
perex@suse.cz, vojtech@suse.cz, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: 2.6.11-mm1: sound <-> GAMEPORT problems
Date: Mon, 7 Mar 2005 17:12:57 -0500 [thread overview]
Message-ID: <d120d50005030714126e345fe2@mail.gmail.com> (raw)
In-Reply-To: <20050307215206.GH3170@stusta.de>
On Mon, 7 Mar 2005 22:52:06 +0100, Adrian Bunk <bunk@stusta.de> wrote:
> On Mon, Mar 07, 2005 at 09:41:59AM +0100, Borislav Petkov wrote:
> > On Friday 04 March 2005 12:32, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11
> > >-mm1/
> > >
> > <snip>
> >
> > Hi,
> >
> > the ymfpci sound driver wouldn't compile without gameport support selected
> > since the sound card has a gameport on it:
> >
> > Signed-off-by: Borislav Petkov <petkov@uni-muenster.de>
> >
> > --- sound/pci/ymfpci/ymfpci.c.orig 2005-03-07 09:07:10.000000000 +0100
> > +++ sound/pci/ymfpci/ymfpci.c 2005-03-07 09:08:02.000000000 +0100
> > @@ -332,7 +332,9 @@ static int __devinit snd_card_ymfpci_pro
> > }
> > }
> >
> > +#ifdef SUPPORT_JOYSTICK
> > snd_ymfpci_create_gameport(chip, dev, legacy_ctrl, legacy_ctrl2);
> > +#endif /* SUPPORT_JOYSTICK */
> >
> > if ((err = snd_card_register(card)) < 0) {
> > snd_card_free(card);
>
> Nice catch (but I had to apply the patch manually due to some
> whitespace damage).
>
> After a quick look, it seems there are a dozen other sound drivers (most
> OSS but also ALSA) with similar problems.
Note that in input tree (and in -mm) I tried to clean up these #ifdefs
by providing dummy functions when CONFIG_GAMEPORT is not selected. The
original report caused by the typo in dummy function name
(snc_ymfpci_create_gameport).
--
Dmitry
next prev parent reply other threads:[~2005-03-07 22:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 11:32 2.6.11-mm1 Andrew Morton
2005-03-04 13:59 ` 2.6.11-mm1 Aurélien Francillon
2005-03-04 14:19 ` 2.6.11-mm1 Aurélien Francillon
2005-03-04 16:44 ` 2.6.11-mm1 (compile stats) John Cherry
2005-03-04 22:16 ` 2.6.11-mm1 Alexander Nyberg
2005-03-04 22:39 ` 2.6.11-mm1 Andrew Morton
2005-03-04 22:55 ` 2.6.11-mm1 Alexander Nyberg
2005-03-08 21:31 ` 2.6.11-mm1 Alexander Nyberg
2005-03-07 8:41 ` 2.6.11-mm1 Borislav Petkov
2005-03-07 21:52 ` 2.6.11-mm1: sound <-> GAMEPORT problems Adrian Bunk
2005-03-07 22:05 ` Dmitry Torokhov
2005-03-07 22:12 ` Dmitry Torokhov [this message]
2005-03-07 23:06 ` [2.6 patch] sound/pci/cs4281.c fix typos in the SUPPORT_JOYSTICK=n case Adrian Bunk
2005-03-08 10:24 ` Vojtech Pavlik
2005-03-09 11:32 ` [2.6 patch] OSS gameport fixes Adrian Bunk
2005-03-10 15:36 ` Dmitry Torokhov
2005-03-10 15:57 ` Vojtech Pavlik
2005-03-07 8:51 ` 2.6.11-mm1 Guillaume Thouvenin
2005-03-07 8:58 ` 2.6.11-mm1 Andrew Morton
2005-03-07 23:45 ` 2.6.11-mm1 Greg KH
2005-03-07 23:07 ` [-mm patch] sound/oss/soundcard.c: remove an unused variable Adrian Bunk
2005-03-08 2:33 ` Jesper Juhl
2005-03-10 17:21 ` 2.6.11-mm1 Tom Rini
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=d120d50005030714126e345fe2@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=dtor_core@ameritech.net \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=petkov@uni-muenster.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