Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964809AbVIMPkV (ORCPT ); Tue, 13 Sep 2005 11:40:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964808AbVIMPkV (ORCPT ); Tue, 13 Sep 2005 11:40:21 -0400 Received: from palinux.external.hp.com ([192.25.206.14]:9355 "EHLO palinux.hppa") by vger.kernel.org with ESMTP id S964805AbVIMPkU (ORCPT ); Tue, 13 Sep 2005 11:40:20 -0400 Date: Tue, 13 Sep 2005 09:40:14 -0600 From: Matthew Wilcox To: Luben Tuikov Cc: Christoph Hellwig , Luben Tuikov , James Bottomley , Linux Kernel Mailing List , SCSI Mailing List Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Message-ID: <20050913154014.GE32395@parisc-linux.org> References: <1126308949.4799.54.camel@mulgrave> <20050910041218.29183.qmail@web51612.mail.yahoo.com> <20050911093847.GA5429@infradead.org> <4325FA6F.3060102@adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4325FA6F.3060102@adaptec.com> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 924 Lines: 16 On Mon, Sep 12, 2005 at 06:00:15PM -0400, Luben Tuikov wrote: > "transport attribute class" is just an _attribute_ class, Christoph. > "transport layer" is a lot more involved. I sincerely hope > you can see this. E.g. domain discovery belongs in the transport > layer. In SPI, LLDDs did it; in MPT the firmware does it. LLDDs having their own domain discovery code is definitely a misfeature. 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. - 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/