From: Matthew Wilcox <willy@infradead.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: hughd@google.com, minchan@kernel.org, ying.huang@intel.com,
ross.zwisler@linux.intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] mm: memory: Introduce new vmf_insert_mixed_mkwrite
Date: Sat, 21 Apr 2018 12:34:09 -0700 [thread overview]
Message-ID: <20180421193409.GD14610@bombadil.infradead.org> (raw)
In-Reply-To: <20180421170540.GA17849@jordon-HP-15-Notebook-PC>
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.
next prev parent reply other threads:[~2018-04-21 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 17:05 Souptick Joarder
2018-04-21 19:34 ` Matthew Wilcox [this message]
2018-04-21 19:41 ` Souptick Joarder
2018-04-23 9:21 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180421193409.GD14610@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=hughd@google.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox