From: "J.A. Magallon" <jamagallon@able.es>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] intel eths for 2.4 [was: Plan for e100-e1000 in mainline]
Date: Thu, 2 May 2002 02:16:43 +0200 [thread overview]
Message-ID: <20020502001643.GE1698@werewolf.able.es> (raw)
In-Reply-To: <20020501010828.GA1753@werewolf.able.es> <3CCF796C.5090401@mandrakesoft.com> <20020501234644.GA1698@werewolf.able.es> <3CD0827B.1050902@mandrakesoft.com>
On 2002.05.02 Jeff Garzik wrote:
>J.A. Magallon wrote:
>
>>On 2002.05.01 Jeff Garzik wrote:
>>
>>>I expect Intel's Q/A to green light their current driver. With a few
>>>patches it should be ready for 2.4.x soon.
>>>
>
>>I did it, taking drivers from 2.5.12, and at least it compiles.
>>I have to try in the real box, but I don't think there were any problems,
>>at least the same than 2.5....
>>
>>Marcelo, is there any chance to get this in next -pre or in .19 ?
>>
>
>When they are suitable for Marcelo, I'm going to send them to Marcelo.
>
>As I wrote in the quoted message, they need some more patches, and I'm
>also interested in feedback from Intel Q/A (which is scheduled for
>sometime this week).
>
Oops, sorry, I misunderstood something.
>If you are interesting in maintaining 2.4.x patches for a short time, go
>for it. But I would rather not have a almost-ready e100 go to Marcelo
>and get released in 2.4.19 in incomplete form. It's out there, it's
>public, let's leave at that for a little while.
>
OK, just forget all about -pre and .19.
If somebody wants to try them, look at one other post about -jam9.
It is the same story, I need them for some new boxen (e1000) and I prefer
to have all in the same tree than apart, so took those from 2.5
instead of Intel's.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre7-jam9 #2 SMP mié may 1 12:09:38 CEST 2002 i686
next prev parent reply other threads:[~2002-05-02 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 1:08 Plan for e100-e1000 in mainline J.A. Magallon
2002-05-01 5:13 ` Jeff Garzik
2002-05-01 14:12 ` Roy Sigurd Karlsbakk
2002-05-01 14:19 ` Steffen Persvold
2002-05-01 23:46 ` [PATCH] intel eths for 2.4 [was: Plan for e100-e1000 in mainline] J.A. Magallon
2002-05-02 0:04 ` Jeff Garzik
2002-05-02 0:16 ` J.A. Magallon [this message]
2002-05-06 10:19 ` Plan for e100-e1000 in mainline Jamie Lokier
2002-05-06 22:25 ` J.A. Magallon
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=20020502001643.GE1698@werewolf.able.es \
--to=jamagallon@able.es \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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