[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFqt6zb74=222mOnpnzLpfXEpttHTgpMitB-TgwrLdHKP3dEkg@mail.gmail.com>
Date: Wed, 18 Apr 2018 16:39:22 +0530
From: Souptick Joarder <jrdr.linux@...il.com>
To: Thierry Reding <thierry.reding@...il.com>
Cc: airlied@...ux.ie, jonathanh@...dia.com,
dri-devel@...ts.freedesktop.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, Matthew Wilcox <willy@...radead.org>
Subject: Re: [PATCH] gpu: drm: tegra: Adding new typedef vm_fault_t
> This new function returns VM_FAULT_NOPAGE only for 0 and -EBUSY, whereas
> we used to return VM_FAULT_NOPAGE for -EAGAIN, -ERESTARTSYS and -EINTR
> as well.
Previously vm_insert_page unable to return VM_FAULT_ type due to which
different drivers
have their own mapping from err to VM_FAULT_ type. With new
vmf_insert_page() introduce
in 4.17-rc1 we have a common mapping for err to VM_FAULT_ which remain
same for every
drivers/file systems.
Was this previously wrong?
I think Matthew is the right person to answer this.
Powered by blists - more mailing lists