On 07/05/2013 08:14 AM, Stephen Rothwell wrote: > On Fri, 05 Jul 2013 08:03:31 +0800 Chen Gang F T > <chen.gang.flying.transfor...@gmail.com> wrote: >> > >> > When a module select "COMPILE_TEST=y" (e.g with allmodconfig), it has >> > right to compile under the architecture which no related HW support. >> > >> > If it can not pass compiling, at least it is not the module's issue, >> > neither the architecture's issue. >> > >> > We have to look for who has duty on it. At least now, it seems only >> > 'asm-generic' can be qualified to play this unlucky role. > You keep saying this, but others have told you that this is not the > problem. >
In real world, it is not the problem. But for 'mad users' (e.g. allmodconfig, randconfig, and me too), they have not provided enough reason for it (prove that is not a problem for 'mad users'). >> > Could you provide your suggestions or completions for this issue ? > If something doesn't build for a particular config, then either it needs > to be fixed or excluded from building in that particular config. I agree with you, if get rid of 'COMPILE_TEST'. Thanks. -- Chen Gang ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
