From: Jeff Garzik <jgarzik@pobox.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org, Roger Luethi <rl@hellgate.ch>
Subject: Re: List of pending v2.4 kernel bugs
Date: Fri, 30 Jul 2004 13:08:07 -0400 [thread overview]
Message-ID: <410A8077.7020308@pobox.com> (raw)
In-Reply-To: <20040730155613.GD2748@logos.cnet>
Marcelo Tosatti wrote:
> On Wed, Jul 21, 2004 at 01:23:36PM +0200, Roger Luethi wrote:
>
>>On Tue, 20 Jul 2004 11:26:40 -0300, Marcelo Tosatti wrote:
>>
>>>I've created a directory to store known pending v2.4 problems,
>>>at http://master.kernel.org/~marcelo/pending-2.4-issues/
>>
>>Multicast is still broken for big-endian architectures using via-rhine
>>(2.4.27-rc3). MC use on BE is rare (no bug reports!), but the bug is
>>fatal for anyone trying that combination. Jeff's got the patch.
>>
>>A couple other drivers may be affected by the same thinko as well.
>
>
> Hi Roger,
>
> I have added your comments in "multicast-bigendian-netdriver" entry
> in the pending bug list.
>
> I asked Jeff about this but he ignored me, again.
Nudge accepted :) I've been more busy than usual.
I am worried because this specific area of code has been "fixed" at
least twice in recent memory, making Roger's changes the third attempt
to address this sort of problem.
I would really like to see verification of patches on the hardware
affected (big endian), as well as tests on little endian to ensure
nothing breaks, before applying them.
Jeff
next prev parent reply other threads:[~2004-07-30 17:08 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 [this message]
2004-07-30 17:29 ` Roger Luethi
2004-07-30 18:10 ` Jeff Garzik
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=410A8077.7020308@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).