From: Juergen Gross <jgross@suse.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Stefano Stabellini <sstabellini@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Garnier <thgarnie@google.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Mathias Krause <minipli@googlemail.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Xen Devel <Xen-devel@lists.xensource.com>,
linux-next@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: manual merge of the xen-tip tree with the tip tree
Date: Mon, 3 Apr 2017 16:55:59 +0200 [thread overview]
Message-ID: <03587cc8-67db-e6be-468a-54072a5db5fa@suse.com> (raw)
In-Reply-To: <20170403143825.GA1124@gmail.com>
On 03/04/17 16:38, Ingo Molnar wrote:
>
> * Juergen Gross <jgross@suse.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,
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Juergen Gross <jgross@suse.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Xen Devel <Xen-devel@lists.xensource.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Andy Lutomirski <luto@kernel.org>,
Mathias Krause <minipli@googlemail.com>,
Thomas Garnier <thgarnie@google.com>
Subject: Re: linux-next: manual merge of the xen-tip tree with the tip tree
Date: Mon, 3 Apr 2017 16:55:59 +0200 [thread overview]
Message-ID: <03587cc8-67db-e6be-468a-54072a5db5fa@suse.com> (raw)
In-Reply-To: <20170403143825.GA1124@gmail.com>
On 03/04/17 16:38, Ingo Molnar wrote:
>
> * Juergen Gross <jgross@suse.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,
Juergen
next prev parent reply other threads:[~2017-04-03 14:55 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 3:35 linux-next: manual merge of the xen-tip tree with the tip tree Stephen Rothwell
2017-03-29 8:37 ` Juergen Gross
2017-03-29 8:59 ` Ingo Molnar
2017-03-29 9:28 ` Juergen Gross
2017-03-29 10:06 ` Vitaly Kuznetsov
2017-04-03 14:38 ` Ingo Molnar
2017-04-03 14:55 ` Juergen Gross [this message]
2017-04-03 14:55 ` Juergen Gross
2017-03-29 9:54 ` Juergen Gross
2017-03-29 10:41 ` Ingo Molnar
2017-03-29 11:13 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-10-28 6:16 Stephen Rothwell
2017-08-31 4:37 Stephen Rothwell
2017-08-31 4:26 Stephen Rothwell
2017-08-31 8:10 ` Thomas Gleixner
2017-08-31 9:00 ` Thomas Gleixner
2017-08-31 9:16 ` Ingo Molnar
2017-08-31 12:36 ` Joe Perches
2017-08-31 10:11 ` Juergen Gross
2017-08-31 12:00 ` Thomas Gleixner
2017-08-31 14:01 ` Boris Ostrovsky
2017-08-31 14:03 ` Juergen Gross
2017-08-31 18:30 ` Thomas Gleixner
2017-08-28 5:20 Stephen Rothwell
2017-08-17 4:03 Stephen Rothwell
2017-06-28 4:21 Stephen Rothwell
2017-04-12 4:30 Stephen Rothwell
2017-04-26 4:57 ` Stephen Rothwell
2017-04-12 4:20 Stephen Rothwell
2017-03-29 3:36 Stephen Rothwell
2017-03-29 3:37 ` Stephen Rothwell
2016-10-03 1:29 Stephen Rothwell
2016-07-26 4:02 Stephen Rothwell
2016-07-26 4:02 ` Stephen Rothwell
2016-07-26 4:01 Stephen Rothwell
2016-07-26 4:01 ` Stephen Rothwell
2016-07-26 13:58 ` Boris Ostrovsky
2016-07-26 13:58 ` Boris Ostrovsky
2016-07-18 6:17 Stephen Rothwell
2016-05-02 4:51 Stephen Rothwell
2016-04-29 4:20 Stephen Rothwell
2015-08-12 5:09 Stephen Rothwell
2015-08-12 13:27 ` Boris Ostrovsky
2015-08-12 17:21 ` Peter Zijlstra
2015-08-12 17:38 ` Peter Zijlstra
2015-08-12 17:46 ` Peter Zijlstra
2015-08-12 18:17 ` Boris Ostrovsky
2015-08-12 18:26 ` Andy Lutomirski
2015-08-12 18:30 ` Boris Ostrovsky
2015-08-12 18:26 ` H. Peter Anvin
2015-08-12 18:36 ` Peter Zijlstra
2015-08-12 18:44 ` Boris Ostrovsky
2015-08-12 19:04 ` Peter Zijlstra
2015-08-13 6:45 ` Ingo Molnar
2014-03-20 4:15 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03587cc8-67db-e6be-468a-54072a5db5fa@suse.com \
--to=jgross@suse.com \
--cc=Xen-devel@lists.xensource.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=minipli@googlemail.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.