Brian Swetland wrote: > We would, of course, prefer to keep the board named mahimahi for all > the reasons that have been mentioned in various previous discussions > around trout, etc: > Ooh, division in the camp. :) Actually, I'd like to change my previous answer. In the interest of getting code into kernel.org more quickly, I for one could live with "mahimahi"--- so long as a comment in board-mahimahi.c provided the "also-known-as" names. Same for board-halibut.c, etc. The point is to document the mapping between the various names _somewhere_ within the kernel code itself. Given that, LXR et. al can help sort things out. I'd prefer the mapping be done with filenames, but mapping in comments is just about as good--- and probably more flexible if a "mahimahi clone" ever appears: no need for another filename, just add to the "also known as" comment. b.g. -- Bill Gatliff Embedded systems training and consulting http://billgatliff.com bgat@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
