linux-kernel - Re: Kernel official involvement

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAErSpo6jdzPZYmtggETE-6k2jRLB7db8t68jQ92GRb1yFSto2g@mail.gmail.com>
Date:	Wed, 4 Jul 2012 08:13:53 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Chris Jones <chrisjones@...n.net.au>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Kernel official involvement

On Wed, Jul 4, 2012 at 6:49 AM, Chris Jones <chrisjones@...n.net.au> 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?

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:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=Documentation/SubmittingPatches;h=c379a2a6949f1c1cac04fb6f185c633512f37061;hb=HEAD
--
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/