| 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: Tue, 16 Jun 2009 12:44:25 -0700 From: "Leo (Hao) Chen" <leochen@...adcom.com> To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm@...ts.arm.linux.org.uk" <linux-arm@...ts.arm.linux.org.uk> cc: "Leo (Hao) Chen" <leochen@...adcom.com> Subject: QUESTION: new arch/arm/mach-bcmring code submission Hi, Our team in Broadcom plan to submit our code of a new ARM11 SoC support to kernel.org. As we have no experience in doing this, I hope that we can get some more information regarding the code submission. 1. We have a whole lot of OS-less csp (chip support package) code that is used in our drivers and arch code. We will release them as GPL but we want to keep and maintain them in our own csp directories. Can we put them under arch/arm/mach-bcmring/csp and arch/arm/mach-bcmring/include/csp directories? If not, what's the proper way to do that? 2. We have driver header files which are currently kept in the include/linux/broadcom directory. Where is the proper place to put our driver header files in Linux kernel? Any guidelines? 3. Do I need to submit our code to any maintainer or just submit to LKML? Thanks a lot, ------------- Leo Hao Chen Software Engineer Broadcom Canada Inc. 604-233-8694 -- 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