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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 20 Sep 2014 15:36:59 +0000 From: Stuart Yoder <stuart.yoder@...escale.com> To: Alexander Graf <agraf@...e.de>, Scott Wood <scottwood@...escale.com> CC: Kim Phillips <Kim.Phillips@...escale.com>, Jose Rivera <German.Rivera@...escale.com>, "<gregkh@...uxfoundation.org>" <gregkh@...uxfoundation.org>, "<arnd@...db.de>" <arnd@...db.de>, "<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>, "<linuxppc-release@...ux.freescale.net>" <linuxppc-release@...ux.freescale.net> Subject: RE: [PATCH 1/4] drivers/bus: Added Freescale Management Complex APIs > Speaking of which, how does Linux find this new bus? I couldn't find > anything that describes the device tree bindings, but maybe I just > missed them. There is a separate thread on the ARM mailing list with the device tree and binding (device tree will be in arch/arm64): http://www.spinics.net/lists/arm-kernel/msg354635.html Stuart
Powered by blists - more mailing lists