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, 26 Feb 2014 11:22:47 -0600 From: Kumar Gala <galak@...eaurora.org> To: Kevin Hilman <khilman@...aro.org> Cc: linux-arm-msm <linux-arm-msm@...r.kernel.org>, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/4] arm: qcom: Split Qualcomm support into legacy and multiplatform On Feb 26, 2014, at 8:22 AM, Kevin Hilman <khilman@...aro.org> wrote: > Kumar Gala <galak@...eaurora.org> writes: > >> Introduce a new mach-qcom that will support SoCs that intend to be >> multiplatform compatiable while keeping mach-msm to legacy SoC/board >> support that will not transition over to multiplatform. >> >> As part of this, we move support for MSM8X60, MSM8960 and MSM8974 over >> to mach-qcom. >> >> Signed-off-by: Kumar Gala <galak@...eaurora.org> > > Having a closer look at this after seeing the multi_v7_defconfig change, > I have a minor nit on the new ARCH_QCOM name. > > For new additions, we've been trying to move towards using SOC_foo > instead of ARCH_foo. Any reason not to do that here also? > > Kevin No reason, just wasn’t aware and no one said anything til now. Hmm, how to handle this now, can we do this as a 3.16 cleanup? - k -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- 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