On Wed, May 23, 2018 at 2:19 PM, Daniel Vetter wrote:
> On Mon, May 21, 2018 at 10:27:44AM +0530, Souptick Joarder wrote:
>> On Thu, May 10, 2018 at 7:18 PM, Souptick Joarder
>> wrote:
>> > On Wed, Apr 25, 2018 at 10:29 AM, Souptick Joarder
>> > wrote:
>> >> Use new return type vm_fault_t for
On Mon, May 21, 2018 at 10:27:44AM +0530, Souptick Joarder wrote:
> On Thu, May 10, 2018 at 7:18 PM, Souptick Joarder
> wrote:
> > On Wed, Apr 25, 2018 at 10:29 AM, Souptick Joarder
> > wrote:
> >> Use new return type vm_fault_t for fault and huge_fault
> >> handler. For now, this is just docum
On Thu, May 10, 2018 at 7:18 PM, Souptick Joarder wrote:
> On Wed, Apr 25, 2018 at 10:29 AM, Souptick Joarder
> wrote:
>> Use new return type vm_fault_t for fault and huge_fault
>> handler. For now, this is just documenting that the
>> function returns a VM_FAULT value rather than an errno.
>> O
On Wed, Apr 25, 2018 at 10:29 AM, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault and huge_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 distinc
Use new return type vm_fault_t for fault and huge_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.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
5 matches
Mail list logo