linux-kernel - Re: linux-next: manual merge of the staging tree with the target-merge tree

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:	Mon, 23 Jul 2012 08:16:53 -0700
From:	Greg KH <greg@...ah.com>
To:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
Cc:	"Michael S. Tsirkin" <mst@...hat.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Stefan Hajnoczi <stefanha@...il.com>,
	Paolo Bonzini <pbonzini@...hat.com>,
	Anthony Liguori <anthony@...emonkey.ws>,
	Zhi Yong Wu <wuzhy@...ibm.com>,
	David Miller <davem@...emloft.net>,
	kvm-devel <kvm@...r.kernel.org>,
	target-devel <target-devel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the staging tree with the
 target-merge tree

On Sun, Jul 22, 2012 at 02:44:23PM -0700, Nicholas A. Bellinger wrote:
> So Linus has merged target-pending/for-next this afternoon, so now we
> are just waiting on net-next to hit mainline with the vhost patches
> already ACK'ed by MST.  Hopefully that makes things easier for you to
> considering taking tcm_vhost upstream via staging.  ;)
> 
> Also, MST asked for an RFC-v5 for the initial merge commit with some
> minor debug wrapper changes that will be going out next week.  This will
> include a move into drivers/staging/tcm_vhost/ against a rebased
> staging.git patch with the necessary -rc0 mainline dependencies.
> 
> Please let me know if your OK with this, otherwise I'll just plan to
> keep -v5 against target-pending/for-next-merge for now, and send a GIT
> PULL after MST gets back from holiday on the 29th -> 30th.

I have no idea what any of the above three paragraphs are asking for, or
talking about, sorry.

Note, the merge window is closed for taking new stuff into the staging
tree.  If it isn't already in my staging-next tree, it isn't going to go
into 3.6 unless it's bug fixes, sorry.  How about we figure all of this
out after 3.6-rc1 is out so we can understand what is going on for 3.7?

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/