linux-kernel - Re: linux-next: Requirements and process

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: <20080502233519.a988b552.akpm@linux-foundation.org>
Date:	Fri, 2 May 2008 23:35:19 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: linux-next: Requirements and process

On Sat, 3 May 2008 15:45:42 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> The following architectures are not in linux-next (and should be):
> 
> alpha		cris		frv
> h8300		m32r		m68knommu
> mips		mn10300		parisc
> um		v850		xtensa

mips, m32r, parisc and xtensa do have git trees.  The rest are mastered as
discrete patches in -mm.

Except for m68knommu, which pops unexpectedly out of the woodwork during
the merge window.  I've asked that this be altered ;)
--
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/