public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915: s/dev->dev_private/to_i915(dev)/
Date: Tue, 13 May 2014 15:24:23 -0700	[thread overview]
Message-ID: <20140513152423.04b1a0fc@jbarnes-desktop> (raw)
In-Reply-To: <20140513145628.4aed25c9@jbarnes-desktop>

On Tue, 13 May 2014 14:56:28 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> On Tue, 13 May 2014 22:22:00 +0200
> Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> 
> > coccinelle is seriously a tool I should have played around with much
> > earlier. Extremely powerful, and extremely dangerous in causing
> > massive conflict hell for everyone else since doing large-scale stuff
> > is so much easier than with sed.
> > 
> > Way, way too easy.
> 
> Why?  For an eventual move to embedding drm_device in i915?
> 
> May as well move over all the rest of the driver internals that use
> drm_device * while you're at it. :)  Would be nice to get rid of the
> typedef too...

Oh I see the typedef is already dead... hoory Jani!

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2014-05-13 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 20:21 [PATCH 1/2] drm/i915: use dev_priv directly in i915_driver_unload Daniel Vetter
2014-05-13 20:22 ` [PATCH 2/2] drm/i915: s/dev->dev_private/to_i915(dev)/ Daniel Vetter
2014-05-13 21:56   ` Jesse Barnes
2014-05-13 22:24     ` Jesse Barnes [this message]
2014-05-14  8:51     ` Jani Nikula
2014-05-14 10:04 ` [PATCH 1/2] drm/i915: use dev_priv directly in i915_driver_unload Damien Lespiau
2014-05-14 11:12   ` 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=20140513152423.04b1a0fc@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --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