Messages in this thread | | | Date | Tue, 17 Apr 2012 13:25:00 +0300 | From | Avi Kivity <> | Subject | Re: [GIT PULL] KVM updates for the 3.4 merge window |
| |
On 04/17/2012 12:34 PM, Alexander Graf wrote: >>> 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. > Or do like I do with Kumar for FSL stuff... his stuff gets pulled via my > > Sounds even easier to me. So how do I get my tree into linux-next?
Send a note to Stephen Rothwell (copied).
-- error compiling committee.c: too many arguments to function
| |