[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANN689HCH9xE3GfQ4qxVrFckJAoXPTwjWDHNanwrT3UR3Yi0Bw@mail.gmail.com>
Date: Thu, 26 Mar 2020 00:13:29 -0700
From: Michel Lespinasse <walken@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
linux-mm <linux-mm@...ck.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Vlastimil Babka <vbabka@...e.cz>,
Matthew Wilcox <willy@...radead.org>,
Liam Howlett <Liam.Howlett@...cle.com>,
Jerome Glisse <jglisse@...hat.com>,
Davidlohr Bueso <dave@...olabs.net>,
David Rientjes <rientjes@...gle.com>,
Hugh Dickins <hughd@...gle.com>, Ying Han <yinghan@...gle.com>
Subject: Re: [PATCH 0/8] Add a new mmap locking API wrapping mmap_sem calls
On Thu, Mar 26, 2020 at 12:02 AM Michel Lespinasse <walken@...gle.com> wrote:
> I think it would be feasible to apply them in the next merge cycle if
> given sufficient approval.
Reading this part back, maybe it sounds more pushy than I intended.
What I meant is that I think the code is ready to be submitted through
the normal channels, whatever release that lands it into.
Powered by blists - more mailing lists