From: Marcelo Tosatti <marcelo@kvack.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: Manfred Spraul <manfred@colorfullife.com>,
netdev@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [PATCH-2.4] forcedeth update to 0.50
Date: Wed, 31 May 2006 17:07:09 -0300 [thread overview]
Message-ID: <20060531200709.GB3432@dmt> (raw)
In-Reply-To: <20060531194345.GA11807@w.ods.org>
On Wed, May 31, 2006 at 09:43:45PM +0200, Willy Tarreau wrote:
> 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).
Alright then - will apply Willy's backport.
prev parent reply other threads:[~2006-05-31 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 22:03 [PATCH-2.4] forcedeth update to 0.50 Willy Tarreau
2006-05-31 5:50 ` Manfred Spraul
2006-05-31 5:54 ` Willy Tarreau
2006-05-31 18:05 ` Marcelo Tosatti
2006-05-31 19:50 ` Manfred Spraul
2006-05-31 19:43 ` Willy Tarreau
2006-05-31 20:07 ` Marcelo Tosatti [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=20060531200709.GB3432@dmt \
--to=marcelo@kvack.org \
--cc=aabdulla@nvidia.com \
--cc=manfred@colorfullife.com \
--cc=netdev@vger.kernel.org \
--cc=willy@w.ods.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).