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]

Message-ID: <20080730145600.7b61a43a@bike.lwn.net>
Date:	Wed, 30 Jul 2008 14:56:00 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Jiri Kosina <jkosina@...e.cz>
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 Wed, 30 Jul 2008 13:09:13 +0200 (CEST)
Jiri Kosina <jkosina@...e.cz> wrote:

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

Clearly it's been known to happen (can you say GRU?).  But I don't know
that has ever really been adopted as an "official" policy.  My
preference would be to lay down the merge window rules as a fairly firm
thing rather than suggest to people that there might be ways to slip
around them sometimes.  But, certainly, I'm not tied to that if we want
to send a different message.

Thanks,

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