Date: Wed, 20 Feb 2008 15:08:50 -0800 (PST)
Message-Id: <20080220.150850.56732755.davem@davemloft.net>
To: tonyb@cybernetics.com
Cc: mcarlson@broadcom.com, mchan@broadcom.com, herbert@gondor.apana.org.au,
       netdev@vger.kernel.org, gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: TG3 network data corruption regression 2.6.24/2.6.23.4
From: David Miller <davem@davemloft.net>
In-Reply-To: <47BCB1E9.8020102@cybernetics.com>
References: <47BB54C2.6090501@cybernetics.com>
	<20080220013824.GA5416@localdomain>
	<47BCB1E9.8020102@cybernetics.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 831
Lines: 19

From: Tony Battersby <tonyb@cybernetics.com>
Date: Wed, 20 Feb 2008 18:04:09 -0500

> The following patch fixes the problem for me.  Do we want to accept this
> patch and call it a day or continue investigating the source of the problem?
> 
> Patch applies to 2.6.24.2, but doesn't apply to 2.6.25-rc.  If everyone
> agrees that this is the right solution, I will resubmit with a proper
> subject line and description.

A chipset bug, if it even exists, should be worked around in the
driver for that hardware.  We shouldn't make every other piece
of hardware in the world suffer too.

--
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/