linux-kernel - Re: Git next: Second stage of cpu

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: <Pine.LNX.4.64.0811050753120.11867@quilx.com>
Date:	Wed, 5 Nov 2008 07:54:39 -0600 (CST)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org, travis@....com
Subject: Re: Git next: Second stage of cpu_alloc patches

On Tue, 4 Nov 2008, Andrew Morton wrote:

> On Tue, 4 Nov 2008 20:56:52 -0600 (CST) Christoph Lameter <cl@...ux-foundation.org> wrote:
>
>> The second stage of the cpu_alloc patchset can be pulled from
>>
>> kernel.org/pub/scm/linux/kernel/git/christoph/work.git cpu_alloc_stage2
>
> Please send the patches for review.  Always.

Well okay can we define a process how to get patches merged with the -next 
tree involved? It was nice when you handled all of this but the last 
version of the cpu_alloc was thrown out of mm because of a -next conflict 
and so it seemed better to go to the source than risk this again.

> I've forgotten how this whole cpu_alloc thing worked and now it's all
> stuffed away in some git tree somewhere.  Oh well, whee...

Ok so post a patchset to lkml and at the same time offer a git tree?

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