linux-next: manual merge of the akpm-current tree with the folio tree

Stephen Rothwell
2022-04-08T05:18:20Z

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

Hi all,

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

mm/migrate.c

between commits:

ffe06786b540 ("mm/migrate: Use a folio in alloc_migration_target()")
c185e494ae0c ("mm/migrate: Use a folio in migrate_misplaced_transhuge_page()")

from the folio tree and commits:

c5b406e86042 ("mm: migrate: use thp_order instead of HPAGE_PMD_ORDER for new page allocation.")
649b74d8bc1a ("mm/migration: fix the confusing PageTransHuge check")
6c9c6f6b597d ("mm/migration: remove unneeded out label")

from the akpm-current tree.

I fixed it up (I used the former changes) 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.