[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170403143825.GA1124@gmail.com>
Date: Mon, 3 Apr 2017 16:38:25 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Juergen Gross <jgross@...e.com>
Cc: Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Stefano Stabellini <sstabellini@...nel.org>,
Xen Devel <Xen-devel@...ts.xensource.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Andy Lutomirski <luto@...nel.org>,
Mathias Krause <minipli@...glemail.com>,
Thomas Garnier <thgarnie@...gle.com>
Subject: Re: linux-next: manual merge of the xen-tip tree with the tip tree
* Juergen Gross <jgross@...e.com> 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
Powered by blists - more mailing lists