From: Takashi Iwai <tiwai@suse.de>
To: "Tien, C.L." <cltien@cmedia.com.tw>
Cc: alsa-devel@alsa-project.org
Subject: Re: als4000 compile error in alsa-driver CVS
Date: Wed, 23 Mar 2005 11:03:48 +0100 [thread overview]
Message-ID: <s5hvf7i1xx7.wl@alsa2.suse.de> (raw)
In-Reply-To: <92C0412E07F63549B2A2F2345D3DB515F7D6BD@cm-msg-02.cmedia.com.tw>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
At Wed, 23 Mar 2005 07:09:09 +0800,
Tien, C.L. wrote:
>
> I got it updated but still got following error, should I also need to update kernel source? My kernel is 2.6.9-1.667 (Fedora Core 3)
>
> CC [M] /home/cltien/work/alsa-cvs/alsa-driver/pci/als4000.o
> In file included from /home/cltien/work/alsa-cvs/alsa-driver/pci/als4000.c:1:
> /home/cltien/work/alsa-cvs/alsa-driver/pci/../alsa-kernel/pci/als4000.c:603:63: macro "gameport_set_phys" passed 3 arguments, but takes just 2
My failure. Try the patch below.
Takashi
[-- Attachment #2: Type: text/plain, Size: 664 bytes --]
Index: alsa-driver/include/adriver.h
===================================================================
RCS file: /home/iwai/cvs/alsa/alsa-driver/include/adriver.h,v
retrieving revision 1.103
diff -u -r1.103 adriver.h
--- alsa-driver/include/adriver.h 22 Mar 2005 17:58:57 -0000 1.103
+++ alsa-driver/include/adriver.h 23 Mar 2005 10:02:46 -0000
@@ -760,7 +760,7 @@
#define gameport_get_port_data(gp) ((struct snd_gameport *)(gp))->port_data
#define gameport_set_dev_parent(gp,xdev)
#define gameport_set_name(gp,x)
-#define gameport_set_phys(gp,x)
+#define gameport_set_phys(gp,x,y)
#endif /* to_gameport_driver */
#endif /* GAMEPORT || GAMEPORT_MODULE */
next prev parent reply other threads:[~2005-03-23 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 23:09 als4000 compile error in alsa-driver CVS "Tien, C.L. - 田承禮"
2005-03-23 10:03 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 19:21 "Tien, C.L. - 田承禮"
2005-03-22 20:46 ` Takashi Iwai
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=s5hvf7i1xx7.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=cltien@cmedia.com.tw \
/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