From: Horms <[EMAIL PROTECTED]> Date: Wed, 8 Feb 2006 12:09:29 +0900 > Unfortunately this seems like it is going to be more tedious than > we first thought. I would guess writing some sort of tool to analyse > symbols and headers is the way to go. Else it seems more or less > impossible to clean up headers, even on a small scale.
It's doable on a small scale, you just have to approach the problem from the other direction. Ie. pick a header file and audit the use of that specific header file across the tree. Folks have done this with headers like linux/sched.h and friends in the past. And it's worthwhile because anything that minimises kernel rebuild when touching a header file helps streamline development. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
