Hi Steve, you are right. Microblaze don't need CONFIG_PPC_something but I keep this in files because it will be easier to move this to better place. I wanted to sort what Microblaze don't use. I need to talk with people from sparc and powerpc what we can move and where. I see the best way to push these files to microblaze/kernel/ and then sychronize them with one patch - all archs together. M >> +#ifdef CONFIG_PPC_PSERIES >> +#include <asm/rtas.h> >> +#include <asm/kdump.h> >> +#include <asm/smp.h> >> +#include <asm/iommu.h> >> +#include <asm/btext.h> >> +#include <asm/machdep.h> >> +#include <asm/pSeries_reconfig.h> >> +#include <asm/phyp_dump.h> >> +#include <asm/kexec.h> >> +#endif > > I don't think we need CONFIG_PPC_PSERIES (multiple times) > >> +#ifdef CONFIG_PPC64 >> +int __initdata iommu_is_off; >> +int __initdata iommu_force_on; >> +unsigned long tce_alloc_start, tce_alloc_end; >> +#endif > > or PPC64 (multiple times > >> +#ifdef CONFIG_PPC32 > > or PPC32 > > Steve > > > > ___________________________ > microblaze-uclinux mailing list > microblaze-uclinux@xxxxxxxxxxxxxx > Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux > Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/ > > -- 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