[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220906165110.07cad9a730c630af4425ca33@linux-foundation.org>
Date: Tue, 6 Sep 2022 16:51:10 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Liam Howlett <liam.howlett@...cle.com>
Cc: "maple-tree@...ts.infradead.org" <maple-tree@...ts.infradead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v14 00/70] Introducing the Maple Tree
On Tue, 6 Sep 2022 19:48:38 +0000 Liam Howlett <liam.howlett@...cle.com> wrote:
> This is the v13 + fixes and still based against mm-unstable
> v6.0-rc1-140-geb22a5b1b495
I merged up this version, thanks.
One fix was missed:
--- a/mm/memory.c~mm-remove-the-vma-linked-list-fix
+++ a/mm/memory.c
@@ -1697,6 +1697,7 @@ static void unmap_single_vma(struct mmu_
/**
* unmap_vmas - unmap a range of memory covered by a list of vma's
* @tlb: address of the caller's struct mmu_gather
+ * @mt: the maple tree
* @vma: the starting vma
* @start_addr: virtual address at which to start unmapping
* @end_addr: virtual address at which to end unmapping
_
OK, tiny, but worrisome. This is one of the reasons why I dislike
replacing patch series like this. Hopefully we can get to the finish
line just with little fixups from now on?
Powered by blists - more mailing lists