Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1717076 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2017-08-22 09:00 +0200 |
| Last post | 2017-08-23 08:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
linux-next: manual merge of the akpm-current tree with the tip tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-08-22 09:00 +0200
Re: linux-next: manual merge of the akpm-current tree with the tip tree Vlastimil Babka <vbabka@suse.cz> - 2017-08-23 08:50 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-08-22 09:00 +0200 |
| Subject | linux-next: manual merge of the akpm-current tree with the tip tree |
| Message-ID | <uhbkm-752-7@gated-at.bofh.it> |
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
init/main.c
between commit:
caba4cbbd27d ("debugobjects: Make kmemleak ignore debug objects")
from the tip tree and commit:
50a7dc046b58 ("mm, page_ext: move page_ext_init() after page_alloc_init_late()")
from the akpm-current 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.
--
Cheers,
Stephen Rothwell
diff --cc init/main.c
index aea41cf8f9a3,c401e5a38af3..000000000000
--- a/init/main.c
+++ b/init/main.c
@@@ -658,9 -651,8 +659,8 @@@ asmlinkage __visible void __init start_
initrd_start = 0;
}
#endif
- page_ext_init();
- debug_objects_mem_init();
kmemleak_init();
+ debug_objects_mem_init();
setup_per_cpu_pageset();
numa_policy_init();
if (late_time_init)
[toc] | [next] | [standalone]
| From | Vlastimil Babka <vbabka@suse.cz> |
|---|---|
| Date | 2017-08-23 08:50 +0200 |
| Subject | Re: linux-next: manual merge of the akpm-current tree with the tip tree |
| Message-ID | <uhxEe-5wU-21@gated-at.bofh.it> |
| In reply to | #1717076 |
On 08/22/2017 08:57 AM, Stephen Rothwell wrote:
> Hi Andrew,
Hi,
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> init/main.c
>
> between commit:
>
> caba4cbbd27d ("debugobjects: Make kmemleak ignore debug objects")
>
> from the tip tree and commit:
>
> 50a7dc046b58 ("mm, page_ext: move page_ext_init() after page_alloc_init_late()")
This patch can be also dropped from mmotm. It was a RFC and review
suggested a different approach which I didn't get to try yet. (The other
patches in the series should be fine to stay in any case).
> from the akpm-current 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.
>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web