linux-kernel - Re: [patch 00/54] [Announce] Microsoft Hyper-V drivers for Linux

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] [day] [month] [year] [list]

Message-ID: <20090721165107.GF14746@kroah.com>
Date:	Tue, 21 Jul 2009 09:51:07 -0700
From:	Greg KH <greg@...ah.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	virtualization@...ts.linux-foundation.org,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	virtualization@...ts.osdl.org, Andi Kleen <andi@...stfloor.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [patch 00/54] [Announce] Microsoft Hyper-V drivers for Linux

On Tue, Jul 21, 2009 at 02:07:40PM +0200, Arnd Bergmann wrote:
> On Monday 20 July 2009, Greg KH wrote:
> > Anyway, I agree, for a "proper" review, I will show the final, cleaned
> > up version, like normal.  But we aren't there just yet, that is why this
> > code is going to live in the staging tree for a while.  Give us some
> > time to get it fixed up.
> 
> I would find it helpful to have them in a git tree (or a branch) that
> I can pull, so I can look at both the original code and the cleaned up
> state.
> 
> Any reason why the patches are not yet in your staging.git?

staging.git is for sending patches to Linus only.  Look in the
MAINTAINERS file for a location of my tree of patches for staging.

If you like git, I'd recommend just using the linux-next tree, as that
always has the latest staging patches in it.

thanks,

greg k-h
--
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/