Re: [PATCH] minimal SAS transport class

> > > that even if my minimal code goes in now there's absolutely no reason > > we can't replace it completely later on. See the evolution of the FC > > transport class. > > Who makes all those decisions? > > More generally, why is SCSI Core not being managed by > Documentation/ManagingStyle?

[2.6 patch] drivers/scsi/constants.c should include scsi_dbg.h

C files should include the files with the prototypes for their global functions. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- linux-2.6.13-rc6-mm1/drivers/scsi/constants.c.old 2005-08-20 14:42:12.0 +0200 +++ linux-2.6.13-rc6-mm1/drivers/scsi/constants.c 2005-08-20 14:43:

Re: [PATCH] minimal SAS transport class

On 08/20/05 05:18, Christoph Hellwig wrote: > On Fri, Aug 19, 2005 at 04:32:15PM -0400, Luben Tuikov wrote: > >>>The current SAS class will only get validated when it actually meets >>>real SAS topologies, which is acceptable in my view just to get this >>>project actually moving; code can always

Re: [PATCH] minimal SAS transport class

On 08/20/05 00:15, [EMAIL PROTECTED] wrote: > Ok, so I guess I owe you a response. I hesitate, as this discussion > always becomes larger than it should. > > There are 2 key points: > - the target id is logical for everything but SPI > - following old SPI behavior, users expect the same devices to

Re: 2.6.13-rc6-mm1

--Andrew Morton <[EMAIL PROTECTED]> wrote (on Friday, August 19, 2005 04:33:31 -0700): > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc6/2.6.13-rc6-mm1/ > > - Lots of fixes, updates and cleanups all over the place. > > - If you have the right debugging options set, t

Re: [PATCH] minimal SAS transport class

On Fri, Aug 19, 2005 at 04:32:15PM -0400, Luben Tuikov wrote: > > The current SAS class will only get validated when it actually meets > > real SAS topologies, which is acceptable in my view just to get this > > project actually moving; code can always be updated later ... > > James, the "current