All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux.bhar at gmail.com (Bharath Vedartham)
Subject: [Linux-kernel-mentees] [PATCH v5 0/1] get_user_pages changes
Date: Sat, 10 Aug 2019 01:08:16 +0530	[thread overview]
Message-ID: <1565379497-29266-1-git-send-email-linux.bhar@gmail.com> (raw)

In this 5th 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 v2
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

WARNING: multiple messages have this Message-ID (diff)
From: linux.bhar@gmail.com (Bharath Vedartham)
Subject: [Linux-kernel-mentees] [PATCH v5 0/1] get_user_pages changes
Date: Sat, 10 Aug 2019 01:08:16 +0530	[thread overview]
Message-ID: <1565379497-29266-1-git-send-email-linux.bhar@gmail.com> (raw)
Message-ID: <20190809193816.Bs4R-NqiCpWNBedJF1EYmBgNw7XEdo_hm-ukzwReU1Q@z> (raw)

In this 5th 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 v2
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

WARNING: multiple messages have this Message-ID (diff)
From: Bharath Vedartham <linux.bhar@gmail.com>
To: jhubbard@nvidia.com, gregkh@linuxfoundation.org,
	sivanich@sgi.com, arnd@arndb.de
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 v5 0/1] get_user_pages changes
Date: Sat, 10 Aug 2019 01:08:16 +0530	[thread overview]
Message-ID: <1565379497-29266-1-git-send-email-linux.bhar@gmail.com> (raw)

In this 5th 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 v2
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


             reply	other threads:[~2019-08-09 19:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 19:38 linux.bhar [this message]
2019-08-09 19:38 ` [Linux-kernel-mentees][PATCH v5 0/1] get_user_pages changes Bharath Vedartham
2019-08-09 19:38 ` [Linux-kernel-mentees] [PATCH " Bharath Vedartham
2019-08-09 19:38 ` [Linux-kernel-mentees] [PATCH v5 1/1] sgi-gru: Remove *pte_lookup functions, Convert to get_user_page*() linux.bhar
2019-08-09 19:38   ` [Linux-kernel-mentees][PATCH " Bharath Vedartham
2019-08-09 19:38   ` [Linux-kernel-mentees] [PATCH " Bharath Vedartham
2019-08-13 14:50   ` sivanich
2019-08-13 14:50     ` [Linux-kernel-mentees][PATCH " Dimitri Sivanich
2019-08-13 14:50     ` [Linux-kernel-mentees] [PATCH " Dimitri Sivanich
2019-08-13 17:23     ` linux.bhar
2019-08-13 17:23       ` [Linux-kernel-mentees][PATCH " Bharath Vedartham
2019-08-13 17:23       ` [Linux-kernel-mentees] [PATCH " Bharath Vedartham
2019-08-13 18:19       ` sivanich
2019-08-13 18:19         ` [Linux-kernel-mentees][PATCH " Dimitri Sivanich
2019-08-13 18:19         ` [Linux-kernel-mentees] [PATCH " Dimitri Sivanich
2019-08-14 17:30         ` linux.bhar
2019-08-14 17:30           ` [Linux-kernel-mentees][PATCH " Bharath Vedartham
2019-08-14 17:30           ` [Linux-kernel-mentees] [PATCH " Bharath Vedartham
2019-08-14 17:38           ` jgg
2019-08-14 17:38             ` [Linux-kernel-mentees][PATCH " Jason Gunthorpe
2019-08-14 17:38             ` [Linux-kernel-mentees] [PATCH " Jason Gunthorpe
2019-08-14 18:00             ` linux.bhar
2019-08-14 18:00               ` [Linux-kernel-mentees][PATCH " Bharath Vedartham
2019-08-14 18:00               ` [Linux-kernel-mentees] [PATCH " Bharath Vedartham
2019-08-18 17:58   ` linux.bhar
2019-08-18 17:58     ` [Linux-kernel-mentees][PATCH " Bharath Vedartham
2019-08-18 17:58     ` [Linux-kernel-mentees] [PATCH " Bharath Vedartham
2019-08-18 18:25     ` sivanich
2019-08-18 18:25       ` [Linux-kernel-mentees][PATCH " Dimitri Sivanich
2019-08-18 18:25       ` [Linux-kernel-mentees] [PATCH " Dimitri Sivanich

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=1565379497-29266-1-git-send-email-linux.bhar@gmail.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.