From: John Hubbard <jhubbard@nvidia.com>
To: Christoph Hellwig <hch@lst.de>, Dan Williams <dan.j.williams@intel.com>
Cc: "Jan Kara" <jack@suse.cz>, "Jérôme Glisse" <jglisse@redhat.com>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux MM" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: Cleanup __put_devmap_managed_page() vs ->page_free()
Date: Wed, 13 Nov 2019 23:26:35 -0800 [thread overview]
Message-ID: <588a955d-0750-b6db-738a-7556704fa894@nvidia.com> (raw)
In-Reply-To: <20191114072354.GA26448@lst.de>
On 11/13/19 11:23 PM, Christoph Hellwig wrote:
> On Wed, Nov 13, 2019 at 04:47:38PM -0800, Dan Williams wrote:
>>> Got it. This will appear in the next posted version of my "mm/gup: track
>>> dma-pinned pages: FOLL_PIN, FOLL_LONGTERM" patchset.
>>
>> Thanks!
>
> John - can you please send a small series just doing the zone device
> patches rework? That way we can review it separately and maybe even get
> it into 5.5.
>
Sure.
thanks,
--
John Hubbard
NVIDIA
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2019-11-14 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 0:07 [PATCH] mm: Cleanup __put_devmap_managed_page() vs ->page_free() Dan Williams
2019-11-14 0:39 ` John Hubbard
2019-11-14 0:47 ` Dan Williams
2019-11-14 7:23 ` Christoph Hellwig
2019-11-14 7:26 ` John Hubbard [this message]
2019-11-14 1:24 ` Jerome Glisse
2019-11-14 7:19 ` Christoph Hellwig
2019-11-14 7:25 ` Dan Williams
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=588a955d-0750-b6db-738a-7556704fa894@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
/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;
as well as URLs for NNTP newsgroup(s).