[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YJmQBp9r5UgvQiWr@casper.infradead.org>
Date: Mon, 10 May 2021 20:56:54 +0100
From: Matthew Wilcox <willy@...radead.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>,
Andrew Morton <akpm@...ux-foundation.org>,
Song Liu <songliubraving@...com>,
Davidlohr Bueso <dave@...olabs.net>,
"Paul E . McKenney" <paulmck@...nel.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
David Rientjes <rientjes@...gle.com>,
Axel Rasmussen <axelrasmussen@...gle.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>,
Michel Lespinasse <michel@...pinasse.org>
Subject: Re: [PATCH] mm/mmap: Introduce unlock_range() for code cleanup
On Mon, May 10, 2021 at 07:50:22PM +0000, Liam Howlett wrote:
> Both __do_munmap() and exit_mmap() unlock a range of VMAs using almost
> identical code blocks. Replace both blocks by a static inline function.
>
> Signed-off-by: Liam R. Howlett <Liam.Howlett@...cle.com>
Reviewed-by: Matthew Wilcox (Oracle) <willy@...radead.org>
> +static inline void unlock_range(struct vm_area_struct *start, unsigned long limit)
Seems like an unnecessary >80 column line ...
static inline
void unlock_range(struct vm_area_struct *start, unsigned long limit)
Powered by blists - more mailing lists