From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jerome Glisse <jglisse@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
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: Tue, 19 Nov 2019 14:49:31 -0400 [thread overview]
Message-ID: <20191119184931.GJ4991@ziepe.ca> (raw)
In-Reply-To: <20191113184943.GA4319@redhat.com>
On Wed, Nov 13, 2019 at 01:49:43PM -0500, Jerome Glisse wrote:
> On Wed, Nov 13, 2019 at 02:45:28PM +0100, Christoph Hellwig wrote:
> > These two functions have never been used since they were added.
>
> The mlx5 convertion (which has been posted few times now) uses them
> dunno what Jason plans is on that front.
IMHO if ODP is going to be the only user then we should just keep the
existing ODP code.
Lets drop them until someone can come up with a series to migrate
several drivers.. It is small so it would not be hard to bring them
back if needed.
So applied to hmm.git
Thanks,
Jason
next prev parent reply other threads:[~2019-11-19 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 13:45 [PATCH] mm/hmm: remove hmm_range_dma_map and hmm_range_dma_unmap Christoph Hellwig
2019-11-13 18:49 ` Jerome Glisse
2019-11-19 18:49 ` Jason Gunthorpe [this message]
2019-11-15 6:18 ` John Hubbard
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=20191119184931.GJ4991@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).