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: <20110317214537.GA28608@suse.de>
Date:	Thu, 17 Mar 2011 14:45:37 -0700
From:	Greg KH <gregkh@...e.de>
To:	Valdis.Kletnieks@...edu
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, Mar 17, 2011 at 05:39:27PM -0400, Valdis.Kletnieks@...edu wrote:
> On Tue, 15 Mar 2011 15:04:54 PDT, Greg KH said:
> 
> > Thanks for the patches, but as the .39 merge window is closed, I'll be
> > holding on to these until after .39-rc1 is out before I can do anything
> > with them.
> 
> 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.

It's been this way for a number of years now, nothing new happening
here...

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.

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/