From: Thierry Reding <thierry.reding@gmail.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: airlied@linux.ie, jonathanh@nvidia.com,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH] gpu: drm: tegra: Adding new typedef vm_fault_t
Date: Mon, 14 May 2018 14:59:36 +0200 [thread overview]
Message-ID: <20180514125936.GL18312@ulmo> (raw)
In-Reply-To: <20180417134755.GA30291@jordon-HP-15-Notebook-PC>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Tue, Apr 17, 2018 at 07:17:55PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
> Reference id -> 1c8f422059ae ("mm: change return type to
> vm_fault_t")
>
> Previously vm_insert_page() returns err which driver
> mapped into VM_FAULT_* type. The new function
> vmf_insert_page() will replace this inefficiency by
> returning VM_FAULT_* type.
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> ---
> drivers/gpu/drm/tegra/gem.c | 18 ++----------------
> 1 file changed, 2 insertions(+), 16 deletions(-)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-14 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 13:47 [PATCH] gpu: drm: tegra: Adding new typedef vm_fault_t Souptick Joarder
2018-04-18 8:24 ` Thierry Reding
2018-04-18 8:24 ` Thierry Reding
2018-04-18 11:09 ` Souptick Joarder
2018-04-23 10:54 ` Matthew Wilcox
2018-05-11 18:20 ` Souptick Joarder
2018-05-14 12:59 ` Thierry Reding [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 16:09 Souptick Joarder
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=20180514125936.GL18312@ulmo \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=willy@infradead.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 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.