From: Miles Lane <miles@megapathdsl.net>
To: "Skip Ford <skip.ford@verizon.net,LKML" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.21 -- emumpu401.c:309: parse error before "emu10k1_midi_init"
Date: Sun, 09 Jun 2002 10:20:32 -0700 [thread overview]
Message-ID: <3D038E60.7030105@megapathdsl.net> (raw)
Skip Ford wrote:
>
> I guess this file also needs init.h
>
>
> --- linux/sound/pci/emu10k1/emumpu401.c~ Sun Jun 9 04:30:46 2002
> +++ linux/sound/pci/emu10k1/emumpu401.c Sun Jun 9 04:31:51 2002
> @@ -22,6 +22,7 @@
> #define __NO_VERSION__
> #include <sound/driver.h>
> #include <linux/time.h>
> +#include <linux/init.h>
> #include <sound/core.h>
> #include <sound/emu10k1.h>
After applying your patch, I get:
gcc -Wp,-MD,.emupcm.o.d -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=athlon -nostdinc -iwithprefix include -DMODULE
-DKBUILD_BASENAME=emupcm -c -o emupcm.o emupcm.c
emupcm.c:964: parse error before "snd_emu10k1_pcm"
emupcm.c:965: warning: return type defaults to `int'
emupcm.c:1012: parse error before "snd_emu10k1_pcm_mic"
emupcm.c:1013: warning: return type defaults to `int'
emupcm.c:1115: parse error before "snd_emu10k1_pcm_efx"
emupcm.c:1116: warning: return type defaults to `int'
make[3]: *** [emupcm.o] Error 1
make[3]: Leaving directory `/usr/src/linux/sound/pci/emu10k1'
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=m
CONFIG_SND_RTCTIMER=m
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_MEMORY=y
CONFIG_SND_DEBUG_DETECT=y
#
# PCI devices
#
CONFIG_SND_EMU10K1=m
next prev reply other threads:[~2002-06-09 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 7:24 2.5.21 -- emumpu401.c:309: parse error before "emu10k1_midi_init" Miles Lane
2002-06-09 8:48 ` Skip Ford
2002-06-09 17:20 ` Miles Lane [this message]
2002-06-09 17:45 ` 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=3D038E60.7030105@megapathdsl.net \
--to=miles@megapathdsl.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox