Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] execbuffer cleanups + fixes
Date: Wed, 12 Oct 2011 09:59:51 -0700	[thread overview]
Message-ID: <20111012095951.68b078bf@bwidawsk.net> (raw)
In-Reply-To: <1318394633-11143-1-git-send-email-ben@bwidawsk.net>

On Tue, 11 Oct 2011 21:43:48 -0700
Ben Widawsky <ben@bwidawsk.net> wrote:

> Some refactors, a bug fixes (found through refactoring), as well as
> setting a bit because the docs says so. That bit is hanging Daniel's
> machine, so we may want to hold off on the last patch for now.
> 
> This patch series is in preparation for some other work I'm doing in
> this area of the code. I think this should be less risky, less
> interesting, and require more nitpicking. That is why I am unleashing it
> now.
> 
> Ben Widawsky (5):
>   drm/i915: execbuffer simplification
>   drm/i915: extract constant offset setting
>   drm/i915: make eb structure do more
>   drm/i915: relative_constants_mode race fix
>   drm/i915: Force sync command ordering (Gen6+)
> 
>  drivers/gpu/drm/i915/i915_gem_execbuffer.c |  188 +++++++++++++++-------------
>  drivers/gpu/drm/i915/i915_reg.h            |    1 +
>  drivers/gpu/drm/i915/intel_ringbuffer.c    |    2 +
>  3 files changed, 105 insertions(+), 86 deletions(-)
> 

As a whole, the series is fine, but I accidentally put a hunk in patch 2 that
belonged in patch 5. Since patch 2 comments specifically say it's just a
refactor (when it's actually a functional change) I think I must nak the
series.

Please continue to comment and give feedback which I can incorporate on the
respin.

Ben

  parent reply	other threads:[~2011-10-12 16:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12  4:43 [PATCH 0/5] execbuffer cleanups + fixes Ben Widawsky
2011-10-12  4:43 ` [PATCH 1/5] drm/i915: execbuffer simplification Ben Widawsky
2011-10-12  4:43 ` [PATCH 2/5] drm/i915: extract constant offset setting Ben Widawsky
2011-10-12 16:46   ` Ben Widawsky
2011-10-12  4:43 ` [PATCH 3/5] drm/i915: make eb structure do more Ben Widawsky
2011-10-12  4:43 ` [PATCH 4/5] drm/i915: relative_constants_mode race fix Ben Widawsky
2011-10-12  4:43 ` [PATCH 5/5] drm/i915: Force sync command ordering (Gen6+) Ben Widawsky
2011-10-12  8:01   ` Ben Widawsky
2011-10-12  9:51   ` Daniel Vetter
2011-10-12 16:59 ` Ben Widawsky [this message]
2011-10-12 22:56 ` [PATCH 0/4] pre-v2 series Ben Widawsky
2011-10-12 22:56   ` [PATCH 1/4] drm/i915: relative_constants_mode race fix Ben Widawsky
2011-10-13  8:35     ` Daniel Vetter
2011-10-13 17:25       ` Ben Widawsky
2011-10-12 22:56   ` [PATCH 2/4] drm/i915: Force sync command ordering (Gen6+) Ben Widawsky
2011-10-13  8:44     ` Daniel Vetter
2011-10-12 22:56   ` [PATCH 3/4] drm/i915: extract constant offset setting Ben Widawsky
2011-10-13  8:46     ` Daniel Vetter
2011-10-13 17:14       ` Ben Widawsky
2011-10-12 22:56   ` [PATCH 4/4] drm/i915: Use eb for more stuff Ben Widawsky
2011-10-13  8:58     ` Daniel Vetter
2011-10-13 12:00       ` Chris Wilson
2011-10-13 12:49         ` Daniel Vetter
2011-10-13 17:31         ` 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=20111012095951.68b078bf@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --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