From: Daniel Vetter <daniel@ffwll.ch>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH v2] drm: remove unnecessary fault wrappers
Date: Tue, 31 Jan 2017 09:40:54 +0100 [thread overview]
Message-ID: <20170131084054.fpognkjdkgwszymv@phenom.ffwll.local> (raw)
In-Reply-To: <20170130221438.GA28713@linux.intel.com>
On Mon, Jan 30, 2017 at 03:14:38PM -0700, Ross Zwisler wrote:
> On Mon, Jan 30, 2017 at 03:09:39PM -0700, Ross Zwisler wrote:
>
> > This patch applies cleanly to mmots/master, which is currently at
> > v4.10-rc5-mmots-2017-01-26-15-49.
>
> Which may not be what you want... The reason I was looking at this code was
> because it was recently changed by Dave Jiang to remove the 'vma' argument
> from all the fault handlers.
>
> So, would you rather:
>
> 1) Take it through the -mm tree to avoid merge conflicts, in which case I'll
> add akpm to the thread.
>
> 2) Take it through your tree & deal with merge conflicts later, in which case
> I can rebase on your tree or on v4.10-rc6.
>
> 3) Just drop it and keep the extra 20 lines or whatever that the complier will
> just optimize out.
>
> I'm fine with any of the above.
drm_vm.c is legacy horror shows, we're not going to touch in in the drm
tree (except for other trivial clenaups). So perfectly fine to merge it
all through -mm.
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2017-01-31 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 19:20 [PATCH] drm: remove unnecessary fault wrappers Ross Zwisler
2017-01-30 20:30 ` Sean Paul
2017-01-30 22:09 ` [PATCH v2] " Ross Zwisler
2017-01-30 22:14 ` Ross Zwisler
2017-01-31 8:40 ` Daniel Vetter [this message]
2017-01-31 14:43 ` Sean Paul
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=20170131084054.fpognkjdkgwszymv@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
/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).