linux-kernel - Re: [PATCH, RFC] A development process document

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 30 Jul 2008 13:09:13 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jonathan Corbet <corbet@....net>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Amanda McPherson <amanda@...pherson.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH, RFC] A development process document

On Tue, 29 Jul 2008, Jonathan Corbet wrote:

> +Over the next six to ten weeks, only patches which fix problems should be
> +submitted to the mainline.  On occasion a more significant change will be
> +allowed, but such occasions are rare; developers who try to merge new
> +features outside of the merge window tend to get an unfriendly reception.
> +As a general rule, if you miss the merge window for a given feature, the
> +best thing to do is to wait for the next development cycle.

On the other hand, the drivers for completely new hardware (that has been 
totally unsupported by the kernel previously, so there is no possibility 
for introducing regressions) are still allowed even after -rc1, right? 

This might be worth explicit note here.

Thanks,

-- 
Jiri Kosina
SUSE Labs

--
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/