You are right, I have tested this. Given that this patch is of no use then, I would like to retract it (it is no longer online). With regard to the short-term solution: at some point of time, say middle January ... begin February, I would like to toss out all unnecessary debugging statements in ccid3 - the amount of debugging output at the moment is enormous and overwhelming.
Quoting Ian McDonald: | Gerrit, | | From memory it is when I do make modules_install that it fails as it | is a linking issue not a compiling issue. The relevant part of the | config is that I've got CCID3 debugging turned on of course. | | Ian | | On 12/19/06, Gerrit Renker <[EMAIL PROTECTED]> wrote: | > Can you please tell me what exactly you are using -- on my computer it compiles without a single error. | > | > | But the EXPORT_SYMBOL_GPL doesn't fix this: | > | > | and now I get this: | > | > | WARNING: Module | > | > | /lib/modules/2.6.20-rc1davem20/kernel/net/dccp/ccids/lib/dccp_tfrc_lib.ko | > | > | ignored, due to loop | > | > | WARNING: Loop detected: | > | > | /home/ian/tmp/lib/modules/2.6.20-rc1davem20/kernel/net/dccp/ccids/dccp_ccid3.ko | > | > | needs dccp_tfrc_lib.ko which needs dccp_ccid3.ko again! | > | > | WARNING: Module | > | > | /lib/modules/2.6.20-rc1davem20/kernel/net/dccp/ccids/dccp_ccid3.ko | > | > | ignored, due to loop | > | > | | > | | - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
