From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Souptick Joarder <jrdr.linux@gmail.com>, linux-mm@kvack.org
Subject: Re: [PATCH] mm: Change return type to vm_fault_t
Date: Thu, 8 Mar 2018 15:48:00 -0800 [thread overview]
Message-ID: <20180308234800.GF29073@bombadil.infradead.org> (raw)
In-Reply-To: <20180308152244.2ba75bc2a766541ab8330eb0@linux-foundation.org>
On Thu, Mar 08, 2018 at 03:22:44PM -0800, Andrew Morton wrote:
> On Thu, 8 Mar 2018 14:22:01 -0800 Matthew Wilcox <willy@infradead.org> wrote:
> > On Thu, Mar 08, 2018 at 06:35:23PM +0530, Souptick Joarder wrote:
> > > Use new return type vm_fault_t for fault handler
> > > in struct vm_operations_struct.
> > >
> > > vmf_insert_mixed(), vmf_insert_pfn() and vmf_insert_page()
> > > are newly added inline wrapper functions.
> > >
> > > Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> >
> > Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
> >
> > Andrew, the plan for these patches is to introduce the typedef, initially
> > just as documentation ("This function should return a VM_FAULT_ status").
> > We'll trickle the patches to individual drivers/filesystems in through
> > the maintainers, as far as possible. In a few months, we'll probably
> > dump a pile of patches to unloved drivers on you for merging. Then we'll
> > change the typedef to an unsigned int and break the compilation of any
> > unconverted driver.
> >
> > Souptick has done a few dozen drivers already, and I've been doing my best
> > to keep up with reviewing the patches submitted. There's some interesting
> > patterns and commonalities between drivers (not to mention a few outright
> > bugs) that we've noticed, and this'll be a good time to clean them up.
>
> OK. All of this should be in the changelog, please. Along with a full
> explanation of the reasons for adding the new functions.
Agreed. Souptick, can you take care of doing that and resubmitting
the patch?
> > It'd be great to get this into Linus' tree sooner so we can start
> > submitting the patches to the driver maintainers.
>
> Sure. I assume that vm_fault_t is `int', so this bare patch won't
> cause a ton of type mismatch warnings?
Exactly so.
next prev parent reply other threads:[~2018-03-08 23:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 13:05 [PATCH] mm: Change return type to vm_fault_t Souptick Joarder
2018-03-08 22:22 ` Matthew Wilcox
2018-03-08 23:22 ` Andrew Morton
2018-03-08 23:48 ` Matthew Wilcox [this message]
2018-03-09 6:28 ` Souptick Joarder
2018-03-08 22:26 ` Andrew Morton
2018-03-08 22:55 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2018-04-14 21:33 Souptick Joarder
2018-05-29 14:31 Souptick Joarder
2018-05-29 14:50 ` Matthew Wilcox
2018-05-29 15:55 ` Souptick Joarder
2018-05-29 17:34 ` Matthew Wilcox
2018-05-30 3:40 ` Souptick Joarder
2018-05-30 11:16 ` Matthew Wilcox
2018-06-02 14:44 ` Souptick Joarder
2018-06-02 14:44 ` Souptick Joarder
2018-06-02 14:55 ` Souptick Joarder
2018-06-02 14:59 ` Luc Van Oostenryck
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=20180308234800.GF29073@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-mm@kvack.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).