linux-kernel - Re: [GIT PULL] KVM updates for the 3.4 merge window

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:	Tue, 17 Apr 2012 10:20:51 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
CC:	Alexander Graf <agraf@...e.de>, Paul Mackerras <paulus@...ba.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	KVM list <kvm@...r.kernel.org>,
	Marcelo Tosatti <mtosatti@...hat.com>,
	Paul Mackerras <paulus@....ibm.com>
Subject: Re: [GIT PULL] KVM updates for the 3.4 merge window

On 04/17/2012 02:05 AM, Benjamin Herrenschmidt wrote:
> On Mon, 2012-04-16 at 15:53 +0300, Avi Kivity wrote:
> > 
> > kvm.git next is exposed to linux-next, where they get tested quite a
> > lot.  Granted it's mostly build testing, and people are unlikely to
> > test
> > kvm there, but they will test the non-kvm bits that creep in there.
> > 
> > > The alternative would be that I don't have a -next tree, just
> > collect patches and immediately send them to Avi. That way the main
> > kvm tree would be broken more often, but at least we don't get these
> > horrible synchronization latencies.
> > 
> > That works too.  Don't post immediately; 2-3 week batches would reduce
> > noise.
>
> Or do like I do with Kumar for FSL stuff... his stuff gets pulled via my
> tree but his tree is in linux-next as well. There's no reason not to do
> that.
>
> That way, his next branch gets linux-next coverage whether it's in my
> tree or not, and I pull when I put the final powerpc-next together,
> which gives me a chance to do a quick vet "just in case" and sort out
> any major conflict before it all goes to Linus.
>

Sure, that works too.

-- 
error compiling committee.c: too many arguments to function

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