Bother. I've now heard "don't touch that tree!" from you and the ARM
folks. I'm trying to be a good neighbor, here, but there is some
cleanup I want to do that crosses port boundaries. (None of this is CML2,
BTW; I'm now addressing problems that are common to CML1 as well.)
What is the right procedure for doing changes like this? Is "don't
touch that tree" a permanent condition, or am I going to get a chance
to clean up the global CONFIG_ namespace after your next merge-down?
Could I ask you to audit your tree and change the prefix on any
CONFIG_ symbols that are private over there? This would make life
easier for my auditing tools (kxref and Stephen Cole's ach script).
That's the main thing I'm after right now -- I want to cut down on
the false positives in my orphaned-symbol reports so that the actual
bugs will stand out.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, Historical Review of Pennsylvania, 1759. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/