On 12/20/06, Arnaldo Carvalho de Melo <arnaldo.melo@xxxxxxxxx> wrote:
The loop comes because dccp_ccid3.ko needs symbols provided by dccp_tfrc_lib.ko, so if we try to export ccid3_pr_debug to be used by dccp_tfrc_lib.ko we'll get the loop, so I guess the right thing to do is to introduce tfrc_pr_debug, that will give us more flexibility, allowing one to select ccid3 debugging, tfrc debugging, both or none. - Arnaldo
I think the right thing to do is not to introduce another level of debugging. People want to debug or they don't in my opinion. I think we should do away with ccid3_pr_debug and ccid2_pr_debug. I always turn them all on or all off when working with testing (or add my own statements in). Ian -- Web: http://wand.net.nz/~iam4 Blog: http://imcdnzl.blogspot.com WAND Network Research Group - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
