| 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: <20090506145626.GC3478@suse.de> Date: Wed, 6 May 2009 07:56:26 -0700 From: Greg KH <gregkh@...e.de> To: prashant@...san.com Cc: linux-kernel@...r.kernel.org Subject: Re: New MIPI driver integration to linux kernel On Wed, May 06, 2009 at 03:38:29PM +0530, prashant@...san.com wrote: > > Hello, > > We are exploring options to integrate a new driver based on MIPI > alliances protocols such as SLIMbus, HSI etc into the linux kernel. We > have done all validation / compliance based on the guidelines provided > in the kernel source (Documentation/Submittingdrivers). > > I want greater details on how to submit a new driver for inclusion in > the linux kernel. I have following queries: > > 1. Who can I contact (xxx) to help me integrate the new driver to the > kernel? I'd be glad to help out. > 2. Do I need to send the source code to xxx, who integrates it to the > kernel or do I need to send a patch for the kernel to xxx? If you have patches, that's the best way. > 3. Since we need to add a new folder in the drivers/<subsystem> - Will > it require some permission from the linux community? Not really "permission", just an agreement that you really do need a new directory is all that is needed. Just post your patches here and we can review it and take it from there. thanks, greg k-h -- 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