From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S268803AbTBZQRF>; Wed, 26 Feb 2003 11:17:05 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S268804AbTBZQRF>; Wed, 26 Feb 2003 11:17:05 -0500
Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:1579 "EHLO
	devserv.devel.redhat.com") by vger.kernel.org with ESMTP
	id <S268803AbTBZQRE>; Wed, 26 Feb 2003 11:17:04 -0500
From: Alan Cox <alan@redhat.com>
Message-Id: <200302261627.h1QGREw17937@devserv.devel.redhat.com>
Subject: Re: Tighten up serverworks workaround.
To: davej@codemonkey.org.uk
Date: Wed, 26 Feb 2003 11:27:14 -0500 (EST)
Cc: torvalds@transmeta.com, alan@redhat.com, linux-kernel@vger.kernel.org
In-Reply-To: <200302261349.h1QDn06X002823@deviant.impure.org.uk> from "davej@codemonkey.org.uk" at Feb 26, 2003 01:49:00 PM
X-Mailer: ELM [version 2.5 PL6]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

> Aparently on rev6 of the LE and above, this workaround
> isn't needed. Lets give it a try, and see what happens

Only if serverworks confirm the rumour. This is a corruptor.