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, 23 Sep 2015 11:19:32 -0700 From: santosh shilimkar <santosh.shilimkar@...cle.com> To: Nishanth Menon <nm@...com>, Santosh Shilimkar <ssantosh@...nel.org> Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags Nishant, On 9/22/2015 9:08 AM, Nishanth Menon wrote: > Keystone2 devices are used on more platforms than just Texas > Instruments reference evaluation platforms called EVMs. Providing a > generic compatible "ti,keystone" is not sufficient to differentiate > various SoC definitions possible on various platforms. So, provide > compatible matches for each SoC family by itself. > > This allows SoC specific logic to be run time handled based on > of_machine_is_compatible("ti,k2hk") or as needed for the dependent > processor instead of needing to use board dependent compatibles that > are needed now. > > Signed-off-by: Nishanth Menon <nm@...com> > --- You need to expand that 'not sufficient' for me. Unless there is genuine case to support this, I would want to avoid this churn. Regards, Santosh -- 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