From: Jeff Garzik <jgarzik@pobox.com>
To: Roger Luethi <rl@hellgate.ch>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: List of pending v2.4 kernel bugs
Date: Fri, 30 Jul 2004 14:10:31 -0400 [thread overview]
Message-ID: <410A8F17.8070401@pobox.com> (raw)
In-Reply-To: <20040730172939.GA24235@k3.hellgate.ch>
Roger Luethi wrote:
> On Fri, 30 Jul 2004 13:08:07 -0400, Jeff Garzik wrote:
> As I have pointed out before, I verified for Linux 2.6 that without
> the patch, multicasting worked on x86 but not on ppc, and that with
> the patch multicasting did work on both platforms. If in 2.4 you prefer
> stability over fixes for bugs nobody complained about that's fine by
> me, though.
> I am more concerned with the remaining drivers that at first glance
> looked like they had the same problem (atp, winbond, tulip_core) in
> 2.6. Did anyone ever test these, or try the patches I posted? The only
> feedback I remember was on typhoon, which looked okay to me and indeed
> turned out to work.
Those are precisely the changes I am talking about. I have no idea if
anybody has verified them, and thus, I don't want to push to mainline
until someone does.
Since you verified the via-rhine change, it is OK to merge.
Jeff
next prev parent reply other threads:[~2004-07-30 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 14:26 List of pending v2.4 kernel bugs Marcelo Tosatti
2004-07-20 19:57 ` Zwane Mwaikambo
2004-07-20 19:32 ` Marcelo Tosatti
2004-07-21 11:23 ` Roger Luethi
2004-07-30 15:56 ` Marcelo Tosatti
2004-07-30 17:08 ` Jeff Garzik
2004-07-30 17:29 ` Roger Luethi
2004-07-30 18:10 ` Jeff Garzik [this message]
2004-07-30 18:20 ` Roger Luethi
2004-08-05 13:33 ` Multicast Driver Testing Quick How-To v 0.3 [was: Re: List of pending v2.4 kernel bugs] Roger Luethi
2004-08-10 3:48 ` David Dillow
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=410A8F17.8070401@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=rl@hellgate.ch \
/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).