linux-kernel - Re: git trees which are not yet in linux-next

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]

Date:	Mon, 05 May 2008 21:40:44 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Pekka J Enberg <penberg@...helsinki.fi>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, sfrench@...ibm.com,
	swhiteho@...hat.com, jeff@...zik.org, ralf@...ux-mips.org,
	drzeus-list@...eus.cx, jack@....cz, cbou@...l.ru,
	jens.axboe@...cle.com, ericvh@...il.com, wim@...ana.be,
	chris@...kel.net, nico@....org, clameter@....com,
	ezk@...sunysb.edu, linux-kernel@...r.kernel.org
Subject: Re: git trees which are not yet in linux-next

Pekka J Enberg wrote:
> Well, I only really have three kinds of patches: (1) testing, (2) 
> for-linus asap (fixes in the middle of a release cycle) and (3) for-linus 
> when the merge window opens. Up until now, I've put (1) in for-mm and 
> after enough exposure (and no bug reports) they graduate into (2) or (3).
> 
> So the problem here is where I put the patches in category (1)?

(1) Testing = (1a) testing isolated changes, (1b) testing in integration 
with other pending changes.  -next is for the latter kind of tests, 
AFAIU with the primary goal of sorting out integration related issues. 
For several reasons --- for example one reason which I saw mentioned was 
to attract more testers than maybe -mm had lately --- we have been asked 
to submit code to -next which has passed (1a)-type testing and had 
appropriate review.

Needless to say, many of us have difficulties to acquire resources 
[time, hardware, test cases/ workloads] for (1) or (1a).  OTOH, 
borrowing -next or -mm for too early test stages will not pay out for 
any of us in the long run.
-- 
Stefan Richter
-=====-==--- -=-= --=-=
http://arcgraph.de/sr/
--
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/