lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 13 Mar 2015 21:30:56 +0100 From: Alexandre Belloni <alexandre.belloni@...e-electrons.com> To: Arnd Bergmann <arnd@...db.de> Cc: linux-arm-kernel@...ts.infradead.org, Nicolas Ferre <nicolas.ferre@...el.com>, linux-kernel@...r.kernel.org, Brian Norris <computersforpeace@...il.com>, Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>, Andrew Victor <linux@...im.org.za> Subject: Re: [PATCH] ARM: at91: force CPU selection On 13/03/2015 at 20:50:59 +0100, Arnd Bergmann wrote : > > > > Actually, I had a closer look today and there is already just one level > > in my current version of patches. > > > > I can put everything under menuconfig ARCH_AT91 but I can't remove > > SOC_SAM_V7 and SOC_SAM_V4_V5 because that is what is used to select > > which dtb should be compiled. > > > > This would also break sama5_defconfig. This is a simple fix but that > > means that it makes it difficult to migrate an existing .config. > > > > I'd say let's keep it that way as this is not broken, unless you really > > want to see SOC_SAM_V7 and SOC_SAM_V4_V5 being removed. > > > > I'm not sure what the latest version looks like, but I think it's fine > to have SOC_SAM_V4_V5 automatically selected when CONFIG_AT91 and > CONFIG_MULTI_V4 || CONFIG_MULTI_V5 are turned on, or selected by > AT91SAM9 and AT91RM9200. > OK, I'm doing that. I'll send v3 in a few minutes. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists