LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Souptick Joarder <jrdr.linux@gmail.com>,
akpm@linux-foundation.org, mhocko@suse.com, hughd@google.com,
dan.j.williams@intel.com, rientjes@google.com,
mike.kravetz@oracle.com, n-horiguchi@ah.jp.nec.com,
aneesh.kumar@linux.vnet.ibm.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH v3] mm: Change return type to vm_fault_t
Date: Fri, 11 May 2018 23:20:29 -0700 [thread overview]
Message-ID: <e194731158f7f89145ed0ae28f46aac5726fc32d.camel@perches.com> (raw)
In-Reply-To: <20180512061712.GA26660@jordon-HP-15-Notebook-PC>
On Sat, 2018-05-12 at 11:47 +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.
trivia:
> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
[]
> @@ -627,7 +627,7 @@ struct vm_special_mapping {
> * If non-NULL, then this is called to resolve page faults
> * on the special mapping. If used, .pages is not checked.
> */
> - int (*fault)(const struct vm_special_mapping *sm,
> + vm_fault_t (*fault)(const struct vm_special_mapping *sm,
> struct vm_area_struct *vma,
> struct vm_fault *vmf);
It'd be nicer to realign the 2nd and 3rd arguments
on the subsequent lines.
vm_fault_t (*fault)(const struct vm_special_mapping *sm,
struct vm_area_struct *vma,
struct vm_fault *vmf);
next prev parent reply other threads:[~2018-05-12 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 6:17 Souptick Joarder
2018-05-12 6:20 ` Joe Perches [this message]
2018-05-12 6:25 ` Souptick Joarder
2018-05-12 6:26 ` Souptick Joarder
2018-05-12 14:24 ` Matthew Wilcox
2018-05-12 19:14 ` Souptick Joarder
2018-05-13 2:51 ` Dan Williams
2018-05-13 8:56 ` Joe Perches
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=e194731158f7f89145ed0ae28f46aac5726fc32d.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=hughd@google.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.com \
--cc=willy@infradead.org \
--subject='Re: [PATCH v3] mm: Change return type to vm_fault_t' \
/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
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).