Skip to contentSkip to conversation

linux-next: manual merge of the liveupdate tree with the mm tree

PATCH Mark Brown 1 participant 1 message Sep 24

Subsystems (3)
lore
Share & tools
lore

Mark Brown

author maintainer
#0 lore raw

Hi all,

Today's linux-next merge of the liveupdate tree got a conflict in:

mm/memblock.c

between commit:

ba13f1f32d96d ("mm: memblock: add missing HugeTLB flag name")

from the mm tree and commit:

05a84ceadf702 ("memblock: rename KHO_SCRATCH to KHO_NOPRSRV")

from the liveupdate 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.

mm/memblock.c +0 -0
diff --cc mm/memblock.c
index ea0de4b5f3568,f5aaa38cfa313..0000000000000
@@@ -2878,8 -2885,7 +2878,8 @@@ static const char * const flagname[] = 
  	[ilog2(MEMBLOCK_DRIVER_MANAGED)] = "DRV_MNG",
  	[ilog2(MEMBLOCK_RSRV_NOINIT)] = "RSV_NIT",
  	[ilog2(MEMBLOCK_RSRV_KERN)] = "RSV_KERN",
- 	[ilog2(MEMBLOCK_KHO_SCRATCH)] = "KHO_SCRATCH",
+ 	[ilog2(MEMBLOCK_KHO_NOPRSRV)] = "KHO_NOPRSRV",
 +	[ilog2(MEMBLOCK_RSRV_HUGETLB)] = "RSV_HUGETLB",
  };
  
  static int memblock_debug_show(struct seq_file *m, void *private)