> I've kicked off IA64 build tests on a native IA64 box and the test > kconfigs are: > > ia64-allmodconfig > ia64-allnoconfig > ia64-defconfig These are all good. Thanks for adding to your testbuild farm. > ia64-randconfig-h001 > ... ia64 hasn't seen any real effort to resolve problems that show up in random configurations - so I'm not surprised that you found some (I might be surprised that you found so few!) I'm not quite sure where to go with these reports though. It looks like the first was from a CONFIG_PRINTK=n kernel. This isn't ever going to be a useful option for ia64. I presume it is there to shave down the size of the kernel by a few hundred bytes on embedded systems ... but with systems starting at 32GB ... this is never going to be significant for ia64. Also mission critical systems will always choose better diagnostics over saving some small amount of memory. So should I juggle header include lines to fix this non-problem? Should I make it go away with a "select PRINTK" line in arch/ia64/Kconfig? Or just tell you that I'm not that into randconfig? -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|