| Message ID | 20181206174417.45fe3e7a@canb.auug.org.au (mailing list archive) |
|---|---|
| State | Not Applicable |
| Headers | show |
| Series | linux-next: manual merge of the akpm-current tree with the powerpc tree | expand |
| Context | Check | Description |
|---|---|---|
| snowpatch_ozlabs/apply_patch | warning | next/apply_patch Patch failed to apply |
| snowpatch_ozlabs/apply_patch | fail | Failed to apply to any branch |
On Thu, Dec 06, 2018 at 05:44:17PM +1100, Stephen Rothwell wrote: > Hi Andrew, > > Today's linux-next merge of the akpm-current tree got conflicts in: > > arch/powerpc/include/asm/book3s/32/pgalloc.h > arch/powerpc/include/asm/nohash/32/pgalloc.h > arch/powerpc/mm/pgtable-book3s64.c > > between commits: > > a95d133c8643 ("powerpc/mm: Move pte_fragment_alloc() to a common location") > 32ea4c149990 ("powerpc/mm: Extend pte_fragment functionality to PPC32") > > from the powerpc tree and commit: > > 913c2d755b39 ("mm: treewide: remove unused address argument from pte_alloc functions") > > from the akpm-current tree. > > I fixed it up (see below, plus the extra merge fix patch) 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. The conflict resolution looks good to me. Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org> thanks, - Joel
diff --git a/arch/powerpc/mm/pgtable-frag.c b/arch/powerpc/mm/pgtable-frag.c index af23a587f019..a7b05214760c 100644 --- a/arch/powerpc/mm/pgtable-frag.c +++ b/arch/powerpc/mm/pgtable-frag.c @@ -95,7 +95,7 @@ static pte_t *__alloc_for_ptecache(struct mm_struct *mm, int kernel) return (pte_t *)ret; } -pte_t *pte_fragment_alloc(struct mm_struct *mm, unsigned long vmaddr, int kernel) +pte_t *pte_fragment_alloc(struct mm_struct *mm, int kernel) { pte_t *pte; diff --git a/arch/powerpc/mm/pgtable_32.c b/arch/powerpc/mm/pgtable_32.c index deda68e02338..5b1e1adeb4d2 100644 --- a/arch/powerpc/mm/pgtable_32.c +++ b/arch/powerpc/mm/pgtable_32.c @@ -48,12 +48,12 @@ __ref pte_t *pte_alloc_one_kernel(struct mm_struct *mm) if (!slab_is_available()) return memblock_alloc(PTE_FRAG_SIZE, PTE_FRAG_SIZE); - return (pte_t *)pte_fragment_alloc(mm, address, 1); + return (pte_t *)pte_fragment_alloc(mm, 1); } pgtable_t pte_alloc_one(struct mm_struct *mm) { - return (pgtable_t)pte_fragment_alloc(mm, address, 0); + return (pgtable_t)pte_fragment_alloc(mm, 0); } void __iomem *
Hi Andrew, Today's linux-next merge of the akpm-current tree got conflicts in: arch/powerpc/include/asm/book3s/32/pgalloc.h arch/powerpc/include/asm/nohash/32/pgalloc.h arch/powerpc/mm/pgtable-book3s64.c between commits: a95d133c8643 ("powerpc/mm: Move pte_fragment_alloc() to a common location") 32ea4c149990 ("powerpc/mm: Extend pte_fragment functionality to PPC32") from the powerpc tree and commit: 913c2d755b39 ("mm: treewide: remove unused address argument from pte_alloc functions") from the akpm-current tree. I fixed it up (see below, plus the extra merge fix patch) 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. From: Stephen Rothwell <sfr@canb.auug.org.au> Date: Thu, 6 Dec 2018 17:41:27 +1100 Subject: [PATCH] fix up for "mm: treewide: remove unused address argument from pte_alloc functions" Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au> --- arch/powerpc/mm/pgtable-frag.c | 2 +- arch/powerpc/mm/pgtable_32.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)