From: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Souptick Joarder <jrdr.linux@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Dan Carpenter <dan.carpenter@oracle.com>, Jan Kara <jack@suse.cz>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm/gup: documentation fix for pin_user_pages*() APIs
Date: Sun, 31 May 2020 15:00:11 +0200 [thread overview]
Message-ID: <CAM9Jb+gvGtmqB0a6uRnsHPP+uP3RTOZRr1rcUdCsxRJHXw0fDg@mail.gmail.com> (raw)
In-Reply-To: <20200529084515.46259-1-jhubbard@nvidia.com>
Acked-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
prev parent reply other threads:[~2020-05-31 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 8:45 [PATCH] mm/gup: documentation fix for pin_user_pages*() APIs John Hubbard
2020-05-29 9:11 ` David Hildenbrand
2020-05-31 6:51 ` Souptick Joarder
2020-05-31 13:00 ` Pankaj Gupta [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=CAM9Jb+gvGtmqB0a6uRnsHPP+uP3RTOZRr1rcUdCsxRJHXw0fDg@mail.gmail.com \
--to=pankaj.gupta.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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).