From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andrew Morton <akpm@osdl.org>,
Gustavo Niemeyer <niemeyer@conectiva.com>,
linux-kernel@vger.kernel.org, jgarzik@pobox.com,
linux-net@vger.kernel.org
Subject: Re: 2.6.0-test4-mm1: wl3501_cs.c doesn't compile
Date: Tue, 26 Aug 2003 12:22:52 -0300 [thread overview]
Message-ID: <20030826152251.GI921@conectiva.com.br> (raw)
In-Reply-To: <20030825220108.GW7038@fs.tum.de>
Em Tue, Aug 26, 2003 at 12:01:08AM +0200, Adrian Bunk escreveu:
> It's attached.
Not needed as per what you said below :)
> I traced the problem down to the gcc version: The file compiles with
> gcc 3.3 but fails to compile with gcc 2.95.
I see, I'll fix this one, I had a problem with this in another source file,
IIRC. Die, gcc 2.95 die! :-)
- Arnaldo
next prev parent reply other threads:[~2003-08-26 15:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 0:13 2.6.0-test4-mm1 Andrew Morton
2003-08-25 6:16 ` pcnet32 oops patches (was Re: 2.6.0-test4-mm1) Barry K. Nathan
2003-08-25 11:00 ` Domen Puncer
2003-08-25 17:30 ` 2.6.0-test4-mm1: wl3501_cs.c doesn't compile Adrian Bunk
2003-08-25 17:46 ` Arnaldo Carvalho de Melo
2003-08-25 18:24 ` Arnaldo Carvalho de Melo
2003-08-25 18:39 ` Arnaldo Carvalho de Melo
2003-08-25 22:01 ` Adrian Bunk
2003-08-26 15:22 ` Arnaldo Carvalho de Melo [this message]
2003-08-25 19:37 ` [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption Barry K. Nathan
2003-08-25 19:45 ` Andrew Morton
2003-08-25 22:54 ` Steve Lord
2003-08-26 10:14 ` Andrew Morton
2003-08-26 11:01 ` Suparna Bhattacharya
2003-08-26 17:44 ` Andrew Morton
2003-08-26 17:57 ` Steve Lord
2003-08-26 18:34 ` Andrew Morton
2003-08-25 23:10 ` 2.6.0-test4-mm1 Martin J. Bligh
2003-08-26 10:08 ` 2.6.0-test4-mm1 William Lee Irwin III
2003-08-26 14:23 ` 2.6.0-test4-mm1 Martin J. Bligh
2003-08-26 14:32 ` 2.6.0-test4-mm1 William Lee Irwin III
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=20030826152251.GI921@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=niemeyer@conectiva.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