| 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
| ||
|
Message-ID: <53F4CAD7.5060904@freescale.com> Date: Wed, 20 Aug 2014 11:20:39 -0500 From: German Rivera <German.Rivera@...escale.com> To: Joe Perches <joe@...ches.com> CC: <gregkh@...uxfoundation.org>, <arnd@...db.de>, <linux-kernel@...r.kernel.org>, <stuart.yoder@...escale.com>, <linuxppc-release@...ux.freescale.net> Subject: Re: [RFC PATCH 1/4 v2] drivers/bus: Added Freescale Management Complex APIs On 08/19/2014 08:19 PM, Joe Perches wrote: > On Tue, 2014-08-19 at 19:54 -0500, J. German Rivera wrote: >> APIs to access the Management Complex (MC) hardware >> module of Freescale LS2 SoCs. This patch includes >> APIs to check the MC firmware version and to manipulate >> DPRC objects in the MC. > [] >> include/linux/fsl_dpmng.h | 120 ++++++ >> include/linux/fsl_dprc.h | 790 ++++++++++++++++++++++++++++++++++++ >> include/linux/fsl_mc_cmd.h | 182 +++++++++ >> include/linux/fsl_mc_sys.h | 50 +++ > > Why should any of these files be put in include/linux? > These header files are going to be shared by more than one of our drivers. Should they be in a new directory under include (such as include/fsl/) or under include/linux (such as include/linux/fsl/)? Thanks, German > -- 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