Kernel official involvement
I am just wondering how does anyone get further involved with Linux kernel development? How do you get selected to be able to push through patches etc. to the official kernel? Who authorizes who to be able to do so?
Regards
Signature · 11 lines
Chris Jones @ [email protected] also on [email protected] and [email protected] OpenSUSE Linux x86_64 (PC)|Android (Smartphone)|Windows 7 (Laptop)|Windows XP (Gaming) Linux kernel developer|Solaris kernel developer|BSD kernel developer Lead Developer of SDL|Lead Developer of Nest Linux|Gamer and Emulator nut|Web Services|Digital Imaging Services Controllers: Rapier V2 Gaming mouse|Logitech Precision|PS3 controller|XB360 controller|Logitech Attack 3 j/stick Emulators: Fusion|Gens|ZSNES|Project64|PCSX-R|Stella|WinVICE|WinUAE|DOSBox PGP Fingerprint: 4E38 0776 B380 63C8 F64F A7D6 736C CF56 42A4 FB35
Quoted 3 lines · Chris Jones
I am just wondering how does anyone get further involved with Linux kernel development? How do you get selected to be able to push through patches etc. to the official kernel? Who authorizes who to be able to do so?
Anyone can write and post kernel patches. There is not really a concept of "people authorized to push patches." In Linux, Linus *pulls* patches that he thinks are useful. He generally pulls patches from maintainers of various areas, who have already reviewed them and decided they are worthwhile. So you just have to convince the maintainer of the area you're changing that your patch is correct and useful. Here are some good hints about how to get started:
Quoted 3 lines · On Wed, 04 Jul 2012 22:49:02 +1000 Chris Jones <[email protected]> wrote:
I am just wondering how does anyone get further involved with Linux kernel development? How do you get selected to be able to push through patches etc. to the official kernel? Who authorizes who to be able to do so?
Please see Documentation/HOWTO and the contents of Documentation/development-process in the kernel source tree; that should tell you everything you need to know.
Thanks,
jon
Jonathan Corbet / LWN.net / [email protected]