[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFqt6zafW0m6V2a6RK=Y+kuhpu3Dg3J+JAdCztZjezDY8_HSiA@mail.gmail.com>
Date: Sun, 22 Apr 2018 01:11:18 +0530
From: Souptick Joarder <jrdr.linux@...il.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Hugh Dickins <hughd@...gle.com>, Minchan Kim <minchan@...nel.org>,
ying.huang@...el.com, Ross Zwisler <ross.zwisler@...ux.intel.com>,
Linux-MM <linux-mm@...ck.org>, linux-kernel@...r.kernel.org,
Al Viro <viro@...iv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH] mm: memory: Introduce new vmf_insert_mixed_mkwrite
On Sun, Apr 22, 2018 at 1:04 AM, Matthew Wilcox <willy@...radead.org> wrote:
> On Sat, Apr 21, 2018 at 10:35:40PM +0530, Souptick Joarder wrote:
>> As of now vm_insert_mixed_mkwrite() is only getting
>> invoked from fs/dax.c, so this change has to go first
>> in linus tree before changes in dax.
>
> No. One patch which changes both at the same time. The history should
> be bisectable so that it compiles and works at every point.
>
> The rest of the patch looks good.
Sure, I will send in a single patch.
Powered by blists - more mailing lists