From: Souptick Joarder <jrdr.linux@gmail.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v2] gpu: drm: armada: Adding new typedef vm_fault_t
Date: Wed, 16 May 2018 10:05:08 +0530 [thread overview]
Message-ID: <CAFqt6zY2amJC4bkRZJgjs7=wCuTTxZbufk9cXcMZLE8VGh_dww@mail.gmail.com> (raw)
In-Reply-To: <20180511092205.GB16141@n2100.armlinux.org.uk>
On Fri, May 11, 2018 at 2:52 PM, Russell King - ARM Linux
<linux@armlinux.org.uk> wrote:
> On Thu, May 10, 2018 at 08:34:48PM +0530, Souptick Joarder wrote:
>> Use new return type vm_fault_t for fault handler in
>> struct vm_operations_struct. 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.
>>
>> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
>>
>> Previously vm_insert_pfn() returns err which driver
>> mapped into VM_FAULT_* type. The new function
>> vmf_insert_pfn() will replace this inefficiency by
>> returning VM_FAULT_* type.
>>
>> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
>> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
>
> Acked-by: Russell King <rmk+kernel@armlinux.org.uk>
>
> Thanks.
If no further comment, we would like to get this patch in queue
for 4.18.
next prev parent reply other threads:[~2018-05-16 4:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:04 [PATCH v2] gpu: drm: armada: Adding new typedef vm_fault_t Souptick Joarder
2018-05-11 9:22 ` Russell King - ARM Linux
2018-05-16 4:35 ` Souptick Joarder [this message]
2018-05-23 9:39 ` Souptick Joarder
2018-06-04 5:16 ` Souptick Joarder
2018-06-19 5:12 ` Souptick Joarder
2018-06-26 15:37 ` Russell King - ARM Linux
2018-06-26 16:07 ` 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='CAFqt6zY2amJC4bkRZJgjs7=wCuTTxZbufk9cXcMZLE8VGh_dww@mail.gmail.com' \
--to=jrdr.linux@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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 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).