From mboxrd@z Thu Jan  1 00:00:00 1970
From: James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [BK PATCH] SCSI -rc fixes for 2.6.10-rc3
Date: Sat, 11 Dec 2004 11:33:32 -0600
Message-ID: <1102786412.5688.13.camel@mulgrave>
References: <1102650988.3814.13.camel@mulgrave>
	 <20041210201115.GD12581@suse.de> <41BA2948.4030906@osdl.org>
	 <1102776407.5688.4.camel@mulgrave>  <20041211172202.GD3033@suse.de>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner+glk-linux-kernel=40m.gmane.org-S261980AbULKReI@vger.kernel.org>
In-Reply-To: <20041211172202.GD3033@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
To: Jens Axboe <axboe@suse.de>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>, SCSI Mailing List <linux-scsi@vger.kernel.org>, Linux Kernel <linux-kernel@vger.kernel.org>
List-Id: linux-scsi@vger.kernel.org

On Sat, 2004-12-11 at 18:22 +0100, Jens Axboe wrote:
> Yep, that would be the optimal. But still, given the hardware, I feel
> the hacky workaround would be acceptable. If Randy wants to fix it
> properly being able to test it, perfect.

Actually, I already put your patch in the scsi-rc-fixes-2.6 tree since
it was obviously correct.  I was just being hopeful ...

James