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, 22 Aug 2014 14:10:23 -0700 From: Andrew Bresticker <abrestic@...omium.org> To: Florian Fainelli <f.fainelli@...il.com> Cc: Kumar Gala <galak@...eaurora.org>, Ralf Baechle <ralf@...ux-mips.org>, David Daney <david.daney@...ium.com>, Rob Herring <robh+dt@...nel.org>, Linux-MIPS <linux-mips@...ux-mips.org>, Qais Yousef <qais.yousef@...tec.com>, Ian Campbell <ijc+devicetree@...lion.org.uk>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Pawel Moll <pawel.moll@....com>, John Crispin <blogic@...nwrt.org>, Mark Rutland <mark.rutland@....com>, Jayachandran C <jchandra@...adcom.com>, Paul Burton <paul.burton@...tec.com>, James Hogan <james.hogan@...tec.com>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, Olof Johansson <olof@...om.net> Subject: Re: [PATCH 0/7] MIPS: Move device-tree files to a common location On Fri, Aug 22, 2014 at 1:42 PM, Florian Fainelli <f.fainelli@...il.com> wrote: > > On Aug 21, 2014 3:05 PM, "Andrew Bresticker" <abrestic@...omium.org> wrote: > > > > To be consistent with other architectures and to avoid unnecessary > > makefile duplication, move all MIPS device-trees to arch/mips/boot/dts > > and build them with a common makefile. > > I recall reading that the ARM organization for DTS files was a bit unfortunate > and should have been something like: > > arch/arm/boot/dts/<vendor>/ > > Is this something we should do for the MIPS and update the other architectures > to follow that scheme? I recall reading that as well and that it would be adopted for ARM64, but that hasn't seemed to have happened. Perhaps Olof (CC'ed) will no more. -- 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