All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Souptick Joarder <jrdr.linux@gmail.com>,
	willy@infradead.org, fbarrat@linux.vnet.ibm.com,
	andrew.donnellan@au1.ibm.com, arnd@arndb.de,
	gregkh@linuxfoundation.org
Cc: brajeswar.linux@gmail.com, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, sabyasachi.linux@gmail.com
Subject: Re: misc: ocxl: Change return type for fault handler
Date: Wed, 11 Jul 2018 23:24:07 +1000 (AEST)	[thread overview]
Message-ID: <41Qft01FR3zB4MS@ozlabs.org> (raw)
In-Reply-To: <20180611202904.GA25538@jordon-HP-15-Notebook-PC>

On Mon, 2018-06-11 at 20:29:04 UTC, 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.
> 
> Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")
> 
> There is an existing bug when vm_insert_pfn() can return
> ENOMEM which was ignored and VM_FAULT_NOPAGE returned as
> default. The new inline vmf_insert_pfn() has removed
> this inefficiency by returning correct vm_fault_ type.
> 
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> Acked-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
> Acked-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/a545cf032d11437ed86e62f00d4991

cheers

  parent reply	other threads:[~2018-07-11 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 20:29 [PATCH] misc: ocxl: Change return type for fault handler Souptick Joarder
2018-06-12  4:39 ` Andrew Donnellan
2018-06-14 16:06 ` Frederic Barrat
2018-06-19  5:09   ` Souptick Joarder
2018-06-19  5:09     ` Souptick Joarder
2018-06-19 12:57     ` Michael Ellerman
2018-06-19 12:57       ` Michael Ellerman
2018-07-11 13:24 ` Michael Ellerman [this message]
2018-07-13 12:57   ` 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=41Qft01FR3zB4MS@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=arnd@arndb.de \
    --cc=brajeswar.linux@gmail.com \
    --cc=fbarrat@linux.vnet.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jrdr.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sabyasachi.linux@gmail.com \
    --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.