From: Bharath Vedartham <linux.bhar@gmail.com>
To: arnd@arndb.de, gregkh@linuxfoundation.org, sivanich@sgi.com,
jhubbard@nvidia.com
Cc: ira.weiny@intel.com, jglisse@redhat.com,
william.kucharski@oracle.com, hch@lst.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel-mentees@lists.linuxfoundation.org,
Bharath Vedartham <linux.bhar@gmail.com>
Subject: [Linux-kernel-mentees][PATCH v4 0/1] get_user_pages changes
Date: Fri, 9 Aug 2019 00:25:54 +0530 [thread overview]
Message-ID: <1565290555-14126-1-git-send-email-linux.bhar@gmail.com> (raw)
In this 4th version of the patch series, I have compressed the patches
of the v2 patch series into one patch. This was suggested by Christoph Hellwig.
The suggestion was to remove the pte_lookup functions and use the
get_user_pages* functions directly instead of the pte_lookup functions.
There is nothing different in this series compared to the previous
series, It essentially compresses the 3 patches of the original series
into one patch.
This series survives a compile test.
Bharath Vedartham (1):
sgi-gru: Remove *pte_lookup functions
drivers/misc/sgi-gru/grufault.c | 112 +++++++++-------------------------------
1 file changed, 24 insertions(+), 88 deletions(-)
--
2.7.4
next reply other threads:[~2019-08-08 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 18:55 Bharath Vedartham [this message]
2019-08-08 18:55 ` [Linux-kernel-mentees][PATCH v4 1/1] sgi-gru: Remove *pte_lookup functions Bharath Vedartham
2019-08-08 23:21 ` John Hubbard
2019-08-08 23:30 ` John Hubbard
2019-08-09 9:44 ` Bharath Vedartham
2019-08-09 9:44 ` Bharath Vedartham
2019-08-09 18:03 ` John Hubbard
2019-08-09 9:52 ` Bharath Vedartham
-- strict thread matches above, loose matches on Subject: below --
2019-07-30 15:39 [Linux-kernel-mentees][PATCH v4 0/1] get_user_pages changes Bharath Vedartham
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=1565290555-14126-1-git-send-email-linux.bhar@gmail.com \
--to=linux.bhar@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sivanich@sgi.com \
--cc=william.kucharski@oracle.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).