On Thu, 2013-07-04 at 10:42 +0800, Chen Gang F T wrote: > Hmm..., I think maybe also has another way: get rid of 'COMPILE_TEST' > (regress the related patch, which is only existent in next-* tree). I'm not working on linux-next at the moment. Hmm, I'm not even working on mainline at the moment, the kernel I have is still 3.10-rc5. > > Or could you provide your suggestions or completions about it ? > > Thanks. > > > I'm still confused by what you are trying to accomplish. > > Currently, I am trying to compile all architectures with allmodconfig in > next-* tree (which will have "COMPILE_TEST=y"). > > So I can find and solve the related issues (I am one of contributors). > So, you want all archs to pass an allmodconfig? Well, one thing is, if a module doesn't build for an arch, then why not keep that module from building for that arch. If module foo.ko doesn't build for arch bazinga, then just add in the Kconfig for the module foo: config FOO depends on !BAZINGA Then that module wont build for the specific arch, and all are happy. If someone someday wants to support module foo for arch bazinga, then they can fix module foo for that arch. -- Steve -- 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
