Jeff Garzik wrote: > James Bottomley wrote: >> SCSI is a slightly different subsystem from almost any other in the >> kernel. It has something like 15 active driver maintainers plus at >> least another 15-25 periodically active ones. Most (but not all) driver >> maintainers are employed by the company who produces the board/chip and >> tend to be overloaded with a lot of non-linux work. (People who do maintenance on a volunteer basis in spare time tend to be overloaded with a lot of non-Linux work too.) >> Requiring acks for >> maintained drivers is a courtesy to make sure we don't get maintainers >> spending time trying to resolve conflicts. I'm not mandating any >> particular method of getting acks, just noting that cc'ing maintainers >> and having specific subject lines mentioning the driver is a reasonable >> way of getting them to notice. > > Linux has never worked that way. We always have a stream of patches > that are multi-subsystem cleanups and the like. Blocking these patches > for months at a time because individual driver maintainers are off doing > non-Linux work is just not realistic. I agree. Merge conflicts and similar issues with such cleanup patches or API conversions and the like are issues which driver maintainers and even subsystem maintainers just have to cope with. Of course it's a different matter with patches which change functionality. The time spent to resolve conflicts - can pay off if overall time to handle patch flow is reduced, - can be minimized by trying to react quickly on simpler patches. -- Stefan Richter -=====-=-=== -=-= ==--= http://arcgraph.de/sr/ - To unsubscribe from this list: 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
