public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre10aa3
Date: Thu, 20 Jun 2002 15:32:49 +0200	[thread overview]
Message-ID: <20020620133249.GG10718@dualathlon.random> (raw)
In-Reply-To: <20020620130511.GA8426@werewolf.able.es>

On Thu, Jun 20, 2002 at 03:05:11PM +0200, J.A. Magallon wrote:
> 
> On 2002.06.20 Andrea Arcangeli wrote:
> >
> >Only in 2.4.19pre10aa3: 07_e100-1.8.38.gz
> >Only in 2.4.19pre10aa3: 08_e100-includes-1
> >Only in 2.4.19pre10aa3: 09_e100-compilehack-1
> >
> >	Merged e100 GPL driver from Intel (also make it link
> >	into the kernel).
> >
> 
> ???
> 
> Current driver is 2.0.30...
> And would not have been easier to get it from 2.5 ? You just have
> good Makefiles, instead of hacking those from Intel, that I suppose
> are prepared for building separate from kernel tree.

I was using this version in an environment and I preferred not to change
this variable because I wouldn't had time to notice if it broke, but of
course I should upgrade soon, thanks for the reminder :). For your tree
you can backout these three patches and apply a more recent version of
course.

> Or just take it from jam2...I have been using both e100 and e1000
> in the same cluster and no problem with them.
> 
> Btw, would you mind mergin also e1000...? ;).

I didn't need it in any environment, and I usually try to avoid any
driver update in -aa except in case I can test it somehow. However if
there's significant request for this I can as well add it (in particular
because it's unlikely to raise maintainance problems).

Andrea

  reply	other threads:[~2002-06-20 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  5:59 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20  6:04 ` 2.4.19pre10aa3 David S. Miller
2002-06-20  6:30   ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 11:44 ` 2.4.19pre10aa3 Andrey Nekrasov
2002-06-20 13:19   ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 17:03     ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 13:05 ` 2.4.19pre10aa3 J.A. Magallon
2002-06-20 13:32   ` Andrea Arcangeli [this message]
2002-06-20 14:07     ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 14:05 ` 2.4.19pre10aa3 Ingo Molnar
2002-06-20 14:40   ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 14:44     ` 2.4.19pre10aa3 Andrea Arcangeli
2002-06-20 15:40 ` 2.4.19pre10aa3 Heinz Diehl
2002-06-20 22:48 ` 2.4.19pre10aa3 J.A. Magallon
2002-06-21  4:31   ` 2.4.19pre10aa3 Andrea Arcangeli

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=20020620133249.GG10718@dualathlon.random \
    --to=andrea@suse.de \
    --cc=jamagallon@able.es \
    --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