From: Ben Hutchings <bhutchings@solarflare.com>
To: Marco Schwarz <marco.schwarz@gmx.net>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: e1000e-1.1.2 Compile errors with 2.4.37 and gcc 2.95.3
Date: Tue, 09 Feb 2010 11:21:49 +0000 [thread overview]
Message-ID: <1265714509.2671.134.camel@localhost> (raw)
In-Reply-To: <20100209095803.236980@gmx.net>
On Tue, 2010-02-09 at 10:58 +0100, Marco Schwarz wrote:
> Hi,
>
> I get the following output when trying to compile e1000e-1.1.2 with Linux Kernel 2.4.37 and gcc 2.95.3 (e1000-8.0.16 compiles fine):
[...]
netdev only deals with recent 2.6 kernels. I'm amazed that Intel still
wastes time on 2.4.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2010-02-09 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 9:58 e1000e-1.1.2 Compile errors with 2.4.37 and gcc 2.95.3 Marco Schwarz
2010-02-09 11:21 ` Ben Hutchings [this message]
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=1265714509.2671.134.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=marco.schwarz@gmx.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).