linux-kernel - Re: [PATCH 00/12] Staging: hv: Cleanup vmbus driver

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: <34155.1300402705@localhost>
Date:	Thu, 17 Mar 2011 18:58:25 -0400
From:	Valdis.Kletnieks@...edu
To:	Greg KH <gregkh@...e.de>
Cc:	"K. Y. Srinivasan" <kys@...rosoft.com>,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	virtualization@...ts.osdl.org
Subject: Re: [PATCH 00/12] Staging: hv: Cleanup vmbus driver - Phase II

On Thu, 17 Mar 2011 14:45:37 PDT, Greg KH said:
> On Thu, Mar 17, 2011 at 05:39:27PM -0400, Valdis.Kletnieks@...edu wrote:
> > Is that Linus's merge window, or your window to freeze a for-linus tree?
> 
> My window.
> 
> Linus's merge window is for the subsystem maintainers.  Everything that
> is to be sent during Linus's merge window had to be in the linux-next
> tree for a bit of time before the merge window opens.

OK, that's what I suspected, but wasn't 100% sure, because..

> I also posted the "my tree is now closed for .39 stuff" message to the
> devel mailing list, so there shouldn't have been any questions about
> this.

some of us are only on lkml, where usually it's Linus who gets to say
"The 2.6.N merge window is closed".

Content of type "application/pgp-signature" skipped