From: Francois Romieu <romieu@fr.zoreil.com>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler version
Date: Sat, 29 May 2004 16:12:47 +0200 [thread overview]
Message-ID: <20040529161247.A19214@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200405291330.i4TDUhsN000547@81-2-122-30.bradfords.org.uk>; from john@grabjohn.com on Sat, May 29, 2004 at 02:30:43PM +0100
John Bradford <john@grabjohn.com> :
[...]
> In my opinion, code that doesn't compile with 2.95.3 is broken - 2.95.3 is
If you are asking for technical details, please read the thread ending
at: http://oss.sgi.com/projects/netdev/archive/2004-05/msg00440.html
[...]
> Basically, 2.95.3 is something of a point of reference, so it only makes
> sense to throw it out once we have a new point of reference.
It makes no sense to religiously recommended 2.95.3 if it is known broken.
If nobody comes with a better approach, I'll simply submit a patch to
remove the 2.95.3 recommendation (+ #error for the driver as suggested by ak).
--
Ueimor
next prev parent reply other threads:[~2004-05-29 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 9:16 Francois Romieu
2004-05-29 9:52 ` Francois Romieu
2004-05-29 13:30 ` John Bradford
2004-05-29 14:12 ` Francois Romieu [this message]
2004-05-29 14:31 ` Adrian Bunk
2004-05-29 14:57 ` John Bradford
2004-05-30 1:18 ` George Georgalis
2004-05-29 14:53 ` John Bradford
2004-05-29 16:58 ` Francois Romieu
[not found] <218aB-15c-17@gated-at.bofh.it>
2004-05-29 10:51 ` Andi Kleen
2004-05-29 14:42 Dan Kegel
2004-05-29 23:55 ` Karim Yaghmour
2004-05-29 23:20 ` Dan Kegel
2004-05-30 0:40 ` Karim Yaghmour
2004-05-30 0:38 ` Karim Yaghmour
2004-05-30 10:37 ` John Bradford
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=20040529161247.A19214@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=john@grabjohn.com \
--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
all inboxes | Powered by JetHome®