From: John Hubbard <jhubbard@nvidia.com>
To: Christoph Hellwig <hch@lst.de>, <jgg@ziepe.ca>, <jglisse@redhat.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/hmm: remove hmm_range_dma_map and hmm_range_dma_unmap
Date: Thu, 14 Nov 2019 22:18:20 -0800 [thread overview]
Message-ID: <688e4271-bedd-c296-6a35-4547191c8f93@nvidia.com> (raw)
In-Reply-To: <20191113134528.21187-1-hch@lst.de>
On 11/13/19 5:45 AM, Christoph Hellwig wrote:
> These two functions have never been used since they were added.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> include/linux/hmm.h | 23 -------
> mm/hmm.c | 147 --------------------------------------------
> 2 files changed, 170 deletions(-)
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
Also +CC Ralph just for another look. But I know we're not using these
routines.
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2019-11-15 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 13:45 Christoph Hellwig
2019-11-13 18:49 ` Jerome Glisse
2019-11-19 18:49 ` Jason Gunthorpe
2019-11-15 6:18 ` John Hubbard [this message]
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=688e4271-bedd-c296-6a35-4547191c8f93@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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