From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030420AbWGTX4J (ORCPT ); Thu, 20 Jul 2006 19:56:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030418AbWGTX4J (ORCPT ); Thu, 20 Jul 2006 19:56:09 -0400 Received: from stat9.steeleye.com ([209.192.50.41]:45235 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S1030417AbWGTX4I (ORCPT ); Thu, 20 Jul 2006 19:56:08 -0400 Subject: Re: [PATCH] Promise 'stex' driver From: James Bottomley To: Jeff Garzik Cc: Ed Lin , "linux-scsi@vger.kernel.org" , hch , linux-kernel , akpm , promise_linux In-Reply-To: <44BFF539.4000700@garzik.org> References: <44BFF539.4000700@garzik.org> Content-Type: text/plain Date: Thu, 20 Jul 2006 19:55:28 -0400 Message-Id: <1153439728.4754.19.camel@mulgrave> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2006-07-20 at 17:27 -0400, Jeff Garzik wrote: > Since _no individual SCSI driver_ uses the block layer > tagging, it is likely that some instability and core kernel > development > will occur, in order to make that work. That's not quite true: 53c700 and tmscsim both use it ... I could with the usage were wider, but at least 53c700 has pretty regular and constant usage ... enough I think to validate the block tag code (it's been using it for the last three years). James