From: Jonathan Corbet <corbet@lwn.net>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: akpm@linux-foundation.org, jack@suse.cz,
kirill.shutemov@linux.intel.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, John Hubbard <jhubbard@nvidia.com>
Subject: Re: [PATCH] docs: mm/gup: Minor documentation update
Date: Fri, 19 Jun 2020 13:26:43 -0600 [thread overview]
Message-ID: <20200619132643.1e9290fc@lwn.net> (raw)
In-Reply-To: <1592422023-7401-1-git-send-email-jrdr.linux@gmail.com>
On Thu, 18 Jun 2020 00:57:03 +0530
Souptick Joarder <jrdr.linux@gmail.com> wrote:
> Now there are 5 cases. Updated the same.
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> Cc: John Hubbard <jhubbard@nvidia.com>
> ---
> Documentation/core-api/pin_user_pages.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/pin_user_pages.rst b/Documentation/core-api/pin_user_pages.rst
> index 6068266..7ca8c7b 100644
> --- a/Documentation/core-api/pin_user_pages.rst
> +++ b/Documentation/core-api/pin_user_pages.rst
> @@ -33,7 +33,7 @@ all combinations of get*(), pin*(), FOLL_LONGTERM, and more. Also, the
> pin_user_pages*() APIs are clearly distinct from the get_user_pages*() APIs, so
> that's a natural dividing line, and a good point to make separate wrapper calls.
> In other words, use pin_user_pages*() for DMA-pinned pages, and
> -get_user_pages*() for other cases. There are four cases described later on in
> +get_user_pages*() for other cases. There are five cases described later on in
> this document, to further clarify that concept.
Applied, thanks.
jon
prev parent reply other threads:[~2020-06-19 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 19:27 Souptick Joarder
2020-06-19 7:22 ` John Hubbard
2020-06-19 19:26 ` Jonathan Corbet [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=20200619132643.1e9290fc@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=jrdr.linux@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®