On Tue, Jul 17, 2007 at 06:24:53AM -0400, Jeff Garzik wrote: > It's just reality that there are never enough people to verify every > patch before it goes in. We just support way too much hardware for that > to be remotely feasible. Sure we -try- to keep the driver maintainer > CC'd, but alas we are human. > Try? I've never _once_ received a CC from you regarding a change to pata_platform. The only time I've been CC'ed at all is when someone submitting the patch had the common courtesy to do so. Whereas the number of times I've had to clean up after something merged behind my back has been higher than the number of times I've been CC'ed on any of these changes. > Your thinking is flawed if you think I'm going to hold up every patch > until it's verified on each of 63 ATA controller drivers, when I make a > core change, for example. Not scalable. We scale in another way: > This has nothing to do with core changes that impact every driver, this has to do with isolated changes to a _single_ driver that you're obviously not in a position to test. That's a very different situation. Again, if you can't be bothered to CC people on changes to their drivers that aren't libata-wide, don't apply them in the first place. I would much rather play API catch up with my driver than have to backtrack and figure out what went wrong when suddenly all of my boards stop booting. Your "merge first and hope someone else notices and fixes it later" approach is insane. We've never done kernel development like that, libata isn't special. - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
