From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: linux-next: manual merge of the xen-tip tree with the tip tree Date: Mon, 3 Apr 2017 16:38:25 +0200 Message-ID: <20170403143825.GA1124@gmail.com> References: <20170329143528.50c0f325@canb.auug.org.au> <906e3014-881c-b1c7-4943-e0ed9845aab2@suse.com> <20170329085945.GA11382@gmail.com> <26fb88f9-dd20-c56b-e87d-6d454b4f7c71@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <26fb88f9-dd20-c56b-e87d-6d454b4f7c71@suse.com> Sender: linux-next-owner@vger.kernel.org To: Juergen Gross Cc: Boris Ostrovsky , Stephen Rothwell , Konrad Rzeszutek Wilk , Stefano Stabellini , Xen Devel , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Vitaly Kuznetsov , Andy Lutomirski , Mathias Krause , Thomas Garnier List-Id: xen-devel@lists.xenproject.org * Juergen Gross wrote: > > So my suggestion would be: could you delay 75cd32d6093e for a week, and then > > merge it on top of a pulled in tip:x86/mm? I'll send that tree to Linus on the > > first day of the merge window so there shouldn't be any ordering problems. > > Okay, that's rather easy to do. > > Boris, I renamed the current Xen for-linus-4.12 branch for easy development of > other Xen patches to for-linus-4.12-pre. > > I'll create another branch for-linus-4.12 based on the tip tree next week which > will be subject to the pull request for Linus. As soon as for-linus-4.12 is > ready the for-linus-4.12-pre branch shouldn't be used any longer. I've created a tip:x86-mm-for-xen branch with the following head: 7f75540ff2ca ("Merge tag 'v4.11-rc5' into x86/mm, to refresh the branch") ... which should be a reasonable base that includes a working version of the 5-level pagetable changes. Thanks, Ingo