From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/7] gtt patches
Date: Thu, 26 Sep 2013 22:34:08 -0700 [thread overview]
Message-ID: <20130927053407.GA4840@bwidawsk.net> (raw)
In-Reply-To: <1380227493-31124-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, Sep 26, 2013 at 10:31:26PM +0200, Daniel Vetter wrote:
> Hi all,
>
> So the first part reworks the gtt ->bind/unbind stuff so that I can rebase the
> -internal try without going berserk. 2nd patch is a bit of fluff removal, next
> for do reorder i915_gem_gtt.c a bit to make more sense (I've been confused every
> 2nd time I've had to rebase -internal and there was a conflict in there, call me
> stupid ...). Last one is my ducttape for the BUG_ON Ville hit.
>
> Cheers, Daniel
>
> Daniel Vetter (7):
> drm/i915: resurrect ->insert_entries/->clear_range gtt interfaces
> drm/i915: don't allow ppgtt enabling to fail anymore
> drm/i915/gtt: group sg setup/teardown functions to the end
> drm/i915/gtt: move restore_gtt_mappings to the bottom
> drm/i915/gtt: group legacy global gtt code together
> drm/i915/gtt: move generic setup code all to the bottom
> drm/i915: we can't call move_to_active before intel_ring_begin
>
> drivers/gpu/drm/i915/i915_dma.c | 4 +-
> drivers/gpu/drm/i915/i915_drv.c | 4 +-
> drivers/gpu/drm/i915/i915_drv.h | 6 +-
> drivers/gpu/drm/i915/i915_gem.c | 8 +-
> drivers/gpu/drm/i915/i915_gem_execbuffer.c | 40 +-
> drivers/gpu/drm/i915/i915_gem_gtt.c | 683 ++++++++++++++---------------
> 6 files changed, 357 insertions(+), 388 deletions(-)
>
At this point it just seems like you're intentionally making it harder
for me to ever merge PPGTT.
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-09-27 5:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 20:31 [PATCH 0/7] gtt patches Daniel Vetter
2013-09-26 20:31 ` [PATCH 1/7] drm/i915: resurrect ->insert_entries/->clear_range gtt interfaces Daniel Vetter
2013-09-26 20:31 ` [PATCH 2/7] drm/i915: don't allow ppgtt enabling to fail anymore Daniel Vetter
2013-09-26 20:31 ` [PATCH 3/7] drm/i915/gtt: group sg setup/teardown functions to the end Daniel Vetter
2013-09-26 20:31 ` [PATCH 4/7] drm/i915/gtt: move restore_gtt_mappings to the bottom Daniel Vetter
2013-09-26 20:31 ` [PATCH 5/7] drm/i915/gtt: group legacy global gtt code together Daniel Vetter
2013-09-26 20:31 ` [PATCH 6/7] drm/i915/gtt: move generic setup code all to the bottom Daniel Vetter
2013-09-26 20:31 ` [PATCH 7/7] drm/i915: we can't call move_to_active before intel_ring_begin Daniel Vetter
2013-09-27 5:34 ` Ben Widawsky [this message]
2013-09-27 19:21 ` [PATCH 0/7] gtt patches Daniel Vetter
2013-09-27 19:29 ` Ben Widawsky
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=20130927053407.GA4840@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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