Chris Friesen writes: > Is there a proper fix other than simply reverting that commit?
It appears that we have a choice between having CONFIG_FTRACE work with gcc 4 and not gcc 3 (the current situation), and having CONFIG_FTRACE work with gcc 3 and not gcc 4 (which is what we would have if that commit was reverted). I think more people use gcc 4 than gcc 3 these days, which is why I haven't reverted that commit. Paul. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
