From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Ralph Campbell" <rcampbell@nvidia.com>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"Jérôme Glisse" <jglisse@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm/doc: add usage description for migrate_vma_*()
Date: Thu, 10 Sep 2020 14:25:14 -0300 [thread overview]
Message-ID: <20200910172514.GN87483@ziepe.ca> (raw)
In-Reply-To: <20200910105657.6007c5ca@lwn.net>
On Thu, Sep 10, 2020 at 10:56:57AM -0600, Jonathan Corbet wrote:
> On Wed, 9 Sep 2020 14:29:56 -0700
> Ralph Campbell <rcampbell@nvidia.com> wrote:
>
> > The migrate_vma_setup(), migrate_vma_pages(), and migrate_vma_finalize()
> > API usage by device drivers is not well documented.
> > Add a description for how device drivers are expected to use it.
> >
> > Signed-off-by: Ralph Campbell <rcampbell@nvidia.com>
> >
> > There shouldn't be any merge conflict with my previous patch which
> > touched hmm.rst but since Jonathan Corbet took my last patch, perhaps he
> > would like to take this one through his tree too.
>
> I'm happy to take it, but it certainly needs an ack from somebody who
> understands HMM better than I do.
Ralph wrote all the in kernel tests for this API, so I think he is
well positioned to write the documentation :)
Jason
next prev parent reply other threads:[~2020-09-10 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 21:29 [PATCH] mm/doc: add usage description for migrate_vma_*() Ralph Campbell
2020-09-10 16:56 ` Jonathan Corbet
2020-09-10 17:25 ` Jason Gunthorpe [this message]
2020-09-15 1:05 ` Alistair Popple
2020-09-16 18:20 ` Jonathan Corbet
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=20200910172514.GN87483@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jglisse@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rcampbell@nvidia.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;
as well as URLs for NNTP newsgroup(s).