Date: Wed, 31 May 2006 21:43:45 +0200
From: Willy Tarreau <willy@w.ods.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Marcelo Tosatti <marcelo@kvack.org>, linux-kernel@vger.kernel.org,
       netdev@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [PATCH-2.4] forcedeth update to 0.50
Message-ID: <20060531194345.GA11807@w.ods.org>
References: <20060530220319.GA6945@w.ods.org> <447D2EA8.8020001@colorfullife.com> <20060531055438.GA9142@w.ods.org> <20060531180545.GA30797@dmt> <447DF38E.3020409@colorfullife.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <447DF38E.3020409@colorfullife.com>
User-Agent: Mutt/1.5.10i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1193
Lines: 35

On Wed, May 31, 2006 at 09:50:38PM +0200, Manfred Spraul wrote:
> Marcelo Tosatti wrote:
> 
> >Since v2.4.33 should be out RSN, my opinion is that applying the 
> >one-liner to fix the bringup problem for now is more prudent..
> >
> > 
> >
> It's attached. Untested, but it should work. Just the relevant hunk from 
> the 0.42 patch.

I will test it tomorrow morning. John might be interested in merging it too,
as I have checked today that RHEL3 was affected by the same problem (rmmod
followed by modprobe).

> But I would disagree with waiting for 2.3.34 for a full backport:
> 0.30 basically doesn't work, thus the update to 0.50 would be a big step 
> forward - it can't be worse that 0.30.

Seconded !
Manfred, if you have some corner cases in mind, are aware of anything which
might sometimes break, or have a few experimental patches to try, I'm OK for
a few tests while I have the machine (it's SMP BTW).

> --
>    Manfred

Cheers,
Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/