[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YiQ6M/FsdHRV41DF@casper.infradead.org>
Date: Sun, 6 Mar 2022 04:36:03 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Jarkko Sakkinen <jarkko@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Nathaniel McCallum <nathaniel@...fian.com>,
Reinette Chatre <reinette.chatre@...el.com>,
linux-sgx@...r.kernel.org, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org, intel-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, codalist@...a.cs.cmu.edu,
linux-unionfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH RFC] mm: Add f_ops->populate()
On Sun, Mar 06, 2022 at 06:25:52AM +0200, Jarkko Sakkinen wrote:
> > Are you deliberately avoiding the question? I'm not asking about
> > implementation. I'm asking about the semantics of MAP_POPULATE with
> > your driver.
>
> No. I just noticed a bug in the guard from your comment that I wanted
> point out.
>
> With the next version I post the corresponding change to the driver,
> in order to see this in context.
Oh, good grief. Don't bother. NAK.
Powered by blists - more mailing lists