public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: oscar.mateo@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/6] drm/i915: Split the ringbuffers from the rings (3/3)
Date: Thu, 22 May 2014 23:44:34 +0200	[thread overview]
Message-ID: <20140522214434.GK14357@phenom.ffwll.local> (raw)
In-Reply-To: <20140522213750.GI14357@phenom.ffwll.local>

On Thu, May 22, 2014 at 11:37:50PM +0200, Daniel Vetter wrote:
> On Thu, May 22, 2014 at 02:13:36PM +0100, oscar.mateo@intel.com wrote:
> > From: Oscar Mateo <oscar.mateo@intel.com>
> > 
> > Manual cleanup after the previous Coccinelle script.
> > 
> > Yes, I could write another Coccinelle script to do this but I
> > don't want labor-replacing robots making an honest programmer's
> > work obsolete (also, I'm lazy).
> 
> Yeah, the tool has serious potential to make us unemployed. Unfortunately
> the documentation is really spotty, and figuring out some of the more
> obscure stuff takes a lot of fiddling :(
> 
> Aside: For reviewing such patches I prefer git diff --word-diff.

One more aside on top: One of the reasons I really like cocci is that it
also makes reviewing such large-scale refactorings easier. But I agree
that for this one here it would have been a bit more fuzz since matching
functions to add the struct intel_ringbuffer *ringbuf local variable is a
bit tricky to do.

Same goes for big sed patches - please add the precise sed filter to the
patch since reviewing that one is much less work than the resulting diff
;-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-05-22 21:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 13:13 [PATCH 0/6] Execlists prep-work oscar.mateo
2014-05-22 13:13 ` [PATCH 1/6] drm/i915: s/intel_ring_buffer/intel_engine_cs oscar.mateo
2014-05-22 13:13 ` [PATCH 2/6] drm/i915: Split the ringbuffers from the rings (1/3) oscar.mateo
2014-05-22 13:13 ` [PATCH 3/6] drm/i915: Split the ringbuffers from the rings (2/3) oscar.mateo
2014-05-22 21:28   ` Daniel Vetter
2014-05-22 13:13 ` [PATCH 4/6] drm/i915: Split the ringbuffers from the rings (3/3) oscar.mateo
2014-05-22 21:37   ` Daniel Vetter
2014-05-22 21:44     ` Daniel Vetter [this message]
2014-05-22 13:13 ` [PATCH 5/6] drm/i915: s/i915_hw_context/intel_context oscar.mateo
2014-05-22 21:39   ` Daniel Vetter
2014-05-22 13:13 ` [PATCH 6/6] drm/i915: Kill private_default_ctx off oscar.mateo
2014-05-22 21:45 ` [PATCH 0/6] Execlists prep-work Daniel Vetter

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=20140522214434.GK14357@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oscar.mateo@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