linux-kernel - Re: [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization"

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1178289450.23670.100.camel@localhost.localdomain>
Date:	Sat, 05 May 2007 00:37:30 +1000
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Andi Kleen <ak@...e.de>, Chris Wright <chrisw@...s-sol.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Zachary Amsden <zach@...are.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure
	for paravirtualization"

On Fri, 2007-05-04 at 08:13 -0600, Eric W. Biederman wrote:
> We don't have any working code, there are no in tree users.

Hi Eric,

	Lack of in-tree code is definitely not due to me.  The code which uses
it has been sitting in -mm for three months.  Suddenly ripping this out
and breaking all that work without replacing it is rude.

> Therefore the code should go.

Then put the patch is -mm, behind lguest.  Or better, help me refine my
patches and I'll happily do it for you.

Of course, I expect that Andrew is about to push my patches to Linus....
any day now... right Andrew?  Then we don't need this argument.

Rusty.


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