linux-kernel - Re: [git pull] cpus4096 tree, part 3

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: <20090103223723.GA17047@elte.hu>
Date:	Sat, 3 Jan 2009 23:37:23 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Nick Piggin <npiggin@...e.de>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Mike Travis <travis@....com>, linux-kernel@...r.kernel.org,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Arjan van de Ven <arjan@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [git pull] cpus4096 tree, part 3


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> What happened to Nick's cleanup patch to do_page_fault (a month or two 
> ago? I complained about some of the issues in his first version and 
> asked for some further cleanups, but I think that whole discussion ended 
> with him saying "I am going to add those changes that you suggested (in 
> fact, I already have)".
> 
> And then I didn't see anything further. Maybe I just missed the end 
> result. Or maybe we have it in some -mm branch or something?

they would have been in tip/x86/mm and would be upstream now had Nick 
re-sent a v2 series but that never happened. I think they might have 
fallen victim to a serious attention deficit caused by the SLQB patch ;-)

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