linux-kernel - Re: [PATCH 1/7] paravirtualization: header and stubs for paravirtualizing critical operations

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]

Date:	Sat, 4 Nov 2006 22:18:03 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Andi Kleen <ak@...e.de>
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Zachary Amsden <zach@...are.com>,
	Chris Wright <chrisw@...s-sol.org>,
	virtualization@...ts.osdl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/7] paravirtualization: header and stubs for
 paravirtualizing critical operations

On Sun, 5 Nov 2006 06:46:15 +0100
Andi Kleen <ak@...e.de> wrote:

> 
> > Andi, the patches work against Andrew's tree, and he's merged them in
> > rc4-mm2.  There are a few warnings to clean up, but it seems basically
> > sound.
> > 
> > At this point I our think time is better spent on beating those patches
> > up, rather than going back and figuring out why they don't work in your
> > tree.
> 
> My tree is basically mainline as base. Sure if you don't care about mainline
> merges we can ignore it there and keep it forever in -mm* until Andrew
> gets tired of it?
> 
> That's a possible strategy, but only if you want to keep it as a mm-only
> toy forever.
> 

They're in my regular list-of-thing-to-spam-maintainers-with, so we can
transfer them as-is next week sometime.

It would be better to sort out the various warnings and any other nasties first
though.

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