Hajime Tazaki <tazaki@xxxxxxxxxxxxxx> writes: > the issue here is the decision between 'no-ops' and > 'assert(false)' depends on the context. an auto-generated > mechanism needs some hand-written parameters I think. Yes, I used auto-generated (fprintf, abort) stubs for similar testing in pettycoin, where if it failed to link it would generate such stubs for undefined symbols. It's not a panacea, but it helps speed up rejiggin after code changes. Generating noop stubs can actually make that process slower, as you can get failures because you now need to do something in that stub. > one more concern on the out-of-arch-tree design is that how > to handle our asm-generic-based header files > (arch/lib/include/asm). we have been heavily used > 'generic-y' in the Kbuild file to reuse header files. Yeah, the arch trick is clever. Cheers, Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
