[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171004072553.GA24620@infradead.org>
Date: Wed, 4 Oct 2017 00:25:53 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Nicolas Pitre <nicolas.pitre@...aro.org>
Cc: Christoph Hellwig <hch@...radead.org>,
Richard Weinberger <richard.weinberger@...il.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
"linux-embedded@...r.kernel.org" <linux-embedded@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Chris Brandt <Chris.Brandt@...esas.com>
Subject: Re: [PATCH v4 4/5] cramfs: add mmap support
On Tue, Oct 03, 2017 at 11:40:28AM -0400, Nicolas Pitre wrote:
> I provided that explanation several times by now in my cover letter. And
> separately even to you directly at least once. What else should I do?
You should do the right things instead of stating irrelevant things
in your cover letter. As said in my last mail: look at the VM_MIXEDMAP
flag and how it is used by DAX, and you'll get out of the vma splitting
business in the fault path.
If the fs/dax.c code scares you take a look at drivers/dax/device.c
instead.
Powered by blists - more mailing lists