On 07/04/2013 09:12 AM, Greg KH wrote: > On Thu, Jul 04, 2013 at 08:57:34AM +0800, Chen Gang wrote: >> > 'COMPILE_TEST=y' will let 'asm-generic' provide self checking sevices to >> > both modules and architectures (especially with allmodconfig and >> > "EXTRA_CFLAGS=-W") > No it doesn't. > "If add 'COMPILE_TEST=y' to 'asm-generic', it will provide self checking services to both modules and architectures" Is it correct ? >> > For modules (especially which will run under the specific architecture >> > soon), the developer can find more compiling issues before they really >> > support it. > Huh? > For developers, they may has hobby to let their code pass compiling as much as possible in the integrating environments, although the modules may not really load/run. >> > For architectures, can let modules compile as much as possible (if >> > "COMPILE_TEST=y"), it will give a better check for the architectures. >> > >> > At present, most of architectures (include various machine/cpu in an >> > architecture) can not pass compiling with 'allmodconfig'. One of the >> > main reasons is the HW of the specific architecture does not support. >> > >> > It is neither architectures issue nor modules issue, the root cause is: >> > "now, 'asm-generic' doesn't provide the related necessary public >> > services for it". > That's not what asm-generic is for at all. Hmm... at least, it is neither architectures issue nor modules issue. So we have to look for who have duty for it, since it is a 'generic' issue for many architectures and modules, we have to find it in 'generic' area (e.g. "./include/*"). At least now, it seems only "asm-generic/*" can play the unlucky role !! Or, do you think it is still the modules issue themselves ? Thanks. -- Chen Gang -- 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
