| 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: Wed, 22 Jan 2014 13:42:40 -0700 From: Stephen Warren <swarren@...dotorg.org> To: Alexandre Courbot <acourbot@...dia.com>, Thierry Reding <thierry.reding@...il.com>, Russell King <linux@....linux.org.uk> CC: Olof Johansson <olof@...om.net>, linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, gnurou@...il.com Subject: Re: [PATCH 3/5] ARM: firmware: enable Trusted Foundations by default On 01/21/2014 03:10 AM, Alexandre Courbot wrote: > As discussed previously (https://lkml.org/lkml/2013/11/26/289), enable > Trusted Foundation support by default since it already depends on a > supporting architecture being selected. > > Doing so allows us to remove it from tegra_defconfig. > arch/arm/configs/tegra_defconfig | 1 - > arch/arm/firmware/Kconfig | 1 + Can we split out the defconfig and code changes into separate patches? They need to go through seperate branches, possibly even separate repos. The defconfig change might not even be necessary; at some point I'll just rebuild it via "make tegra_defconfig; make savedefconfig" on top of some linux-next that includes the Kconfig change, and it'll happen automatically. Still, I guess there's no harm explicitly sending the patch. -- 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