On Tue, 2006-05-16 at 12:12 -0400, Jeff Garzik wrote: > Its an API-which-only-libata-uses that we're discussing. And because > its moving to the block layer, its also a > temporary-API-which-only-libata-uses. OK ... this may be the root of the problem. I really would like libata to migrate to being block only ... especially as PATA looks to be trying to follow you into the SCSI subsystem. However, this has been the statement for the past two years (at least), and really, few enhancements have been made to block that you need to make good on this. I think one of the things we'll try to find time to do at the storage summit is to take a hard look at block to see exactly what has to be added to make libata solely dependent upon it. However, the bottom line is that if you want to modify the *SCSI* API then you follow the same process as everyone else (i.e. demonstrate justification and utility and worry about long lived maintainability of the API). James - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
