From: john slee <indigoid@higherplane.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: dake@staszic.waw.pl, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11-pre3 [gus_midi.c breakage]
Date: Sun, 12 Nov 2000 20:58:48 +1100 [thread overview]
Message-ID: <20001112205848.E19275@higherplane.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10011111914170.7609-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10011111914170.7609-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Sat, Nov 11, 2000 at 07:22:06PM -0800
On Sat, Nov 11, 2000 at 07:22:06PM -0800, Linus Torvalds wrote:
>-----
> - pre3:
> - Bartlomiej Zolnierkiewicz: sound and drm driver init fixes and
> cleanups
this breaks for me, gcc 2.95.2:
gus_midi.c:206: parse error before `gus_midi_init'
gus_midi.c:207: warning: return-type defaults to `int'
gus_midi.c:207: conflicting types for `gus_midi_init'
gus.h:26: previous declaration of `gus_midi_init'
gus_midi.c: In function `gus_midi_init':
gus_midi.c:213: warning: `return' with no value, in function returning non-void
gus_midi.c:221: warning: `return' with no value, in function returning non-void
j.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-12 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-12 3:22 2.4.0-test11-pre3 Linus Torvalds
2000-11-12 9:01 ` 2.4.0-test11-pre3 - md.c compile error Eyal Lebedinsky
2000-11-12 9:58 ` john slee [this message]
2000-11-12 11:17 ` 2.4.0-test11-pre3 [gus_midi.c breakage] Rasmus Andersen
2000-11-12 11:31 ` Rasmus Andersen
2000-11-12 19:15 ` Rasmus Andersen
2000-11-12 10:16 ` 2.4.0-test11-pre3 Geert Uytterhoeven
2000-11-15 15:17 ` 2.4.0-test11-pre3 Tim Waugh
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=20001112205848.E19275@higherplane.net \
--to=indigoid@higherplane.net \
--cc=dake@staszic.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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