Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1440311

Re: linux-next: manual merge of the tip tree with the kspp tree

From Ingo Molnar <mingo@kernel.org>
Newsgroups linux.kernel
Subject Re: linux-next: manual merge of the tip tree with the kspp tree
Date 2016-07-11 09:20 +0200
Message-ID <rTDFv-3Qt-11@gated-at.bofh.it> (permalink)
References <rTBNo-2FZ-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


* Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> Today's linux-next merge of the tip tree got a conflict in:
> 
>   arch/x86/kernel/x86_init.c
> 
> between commit:
> 
>   255303026193 ("x86: apply more __ro_after_init and const")
> 
> from the kspp tree and commit:

Kees, did you plan to submit this patch (and any other pending x86 patches) to the 
x86 tree?

> 
>   1bf8915ae515 ("x86/tsc: Enumerate SKL cpu_khz and tsc_khz via CPUID")
> 
> from the tip tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.

Looks good to me!

Thanks,

	Ingo

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

linux-next: manual merge of the tip tree with the kspp tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-07-11 07:20 +0200
  Re: linux-next: manual merge of the tip tree with the kspp tree Ingo Molnar <mingo@kernel.org> - 2016-07-11 09:20 +0200
    Re: linux-next: manual merge of the tip tree with the kspp tree Kees Cook <keescook@google.com> - 2016-07-11 20:10 +0200

csiph-web