From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Date: Wed, 14 Sep 2005 06:53:23 -0400 Message-ID: <43280123.1020700@pobox.com> References: <1126308949.4799.54.camel@mulgrave> <20050910041218.29183.qmail@web51612.mail.yahoo.com> <20050911093847.GA5429@infradead.org> <4325FA6F.3060102@adaptec.com> <20050913154014.GE32395@parisc-linux.org> <1126677387.26050.71.camel@sipan.sipan.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail.dvmed.net ([216.237.124.58]:50604 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S932717AbVINK4A (ORCPT ); Wed, 14 Sep 2005 06:56:00 -0400 In-Reply-To: <1126677387.26050.71.camel@sipan.sipan.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Sergey Panov Cc: Matthew Wilcox , Luben Tuikov , Christoph Hellwig , Luben Tuikov , James Bottomley , Linux Kernel Mailing List , SCSI Mailing List Sergey Panov wrote: > On Tue, 2005-09-13 at 09:40 -0600, Matthew Wilcox wrote: >>As you know, stuff is being rearranged to move more of the SPI-specific >>code from both SCSI core and LLDDs into the SPI transport. I suspect >>domain discovery will always be triggered by the LLDD for SPI, but at >>least a driver doesn't have to have its own code to do that any more. > Only if it can be turned into a some sort of library LLDD may use if it > needs it. But it is only makes sense to move that code out of the LLDD > and into the transport module, if more then one LLDD can make use of it. ...and in this thread, SAS, more than one LLDD -should- be able to make use it of. ServerWorks/Broadcom SAS+SATA hardware, for which I will soon be writing a driver, has exactly the same needs as Adaptec SAS+SATA hardware. Jeff