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: <19f34abd0811051312o1fe733d8g4d0075aa7eefa964@mail.gmail.com>
Date:	Wed, 5 Nov 2008 22:12:04 +0100
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"Christoph Lameter" <cl@...ux-foundation.org>,
	"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 Wed, Nov 5, 2008 at 5:27 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> We need to get alpha sorted out too.  Frankly, if we can't get anyone to
> review/test/ack the alpha genirq conversion then I'd say merge it
> anyway.  I'll make sure that it at least compiles.

Sounds like a bad strategy. What are these patches you're talking
about, and where can I find them?

I mean, isn't "merge anyway" the same as admitting defeat? I thought
we were going for 100% "review coverage".


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/