All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/i915: s/dev->dev_private/to_i915(dev)/
Date: Wed, 14 May 2014 11:51:32 +0300	[thread overview]
Message-ID: <877g5o3fqj.fsf@intel.com> (raw)
In-Reply-To: <20140513145628.4aed25c9@jbarnes-desktop>

On Wed, 14 May 2014, 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?

Looks like the reason for this change is clearly explained in the commit
message above! :p

Jani.

-- 
Jani Nikula, Intel Open Source Technology Center

  parent reply	other threads:[~2014-05-14  8:51 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
2014-05-14  8:51     ` Jani Nikula [this message]
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=877g5o3fqj.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.