On Mon, 2006-06-26 at 18:23 -0600, Dax Kelson wrote: > On Mon, 2006-06-26 at 09:48 -0500, James Bottomley wrote: > > Not the world perhaps, but I'm unwilling to concede that if a driver > > author is given a list of major issues and does nothing, then the driver > > should go in after everyone gets impatient. > > That isn't accurate or fair. Erich has submitted large patches to > address issues. That hardly qualifies as "does nothing". Yes, that was unfair, and I apologise for it. However ... > > The list of issues is here: > > > > http://marc.theaimsgroup.com/?l=linux-scsi&m=114556263632510 > > > > Most of the serious stuff is fixed with the exception of: > > > > - sysfs has more than one value per file > > - BE platform support > > - PAE (cast of dma_addr_t to unsigned long) issues. > > - SYNCHRONIZE_CACHE is ignored. This is wrong. The sync cache in the > > shutdown notifier isn't sufficient. > > > > At least the sysfs files have to be fixed before it goes in ... unless > > you want to be lynched by Greg? > > Thanks for the new list. Erich has been eager to get work on any > remaining blockers. This isn't a new list. It's extracted from the old list summary of serious issues which an inspection of the driver reveals to be still unresolved. The original list was posted on 20 April http://marc.theaimsgroup.com/?l=linux-scsi&m=114556263632510 And that one was an redux of a previously posed list that I can't be bothered to find. > It would have been nice to have gotten it back on May 19th, they might > have been resolved by now. > > http://marc.theaimsgroup.com/?l=linux-kernel&m=114801926400287&w=2 Well, this is what's adding to the rising frustration ... there's apparently been another hiatus where I thought someone was working on the rest of the issues labelled serious and no-one was. 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
