From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 9/9] drm/i915: drop the typedef for drm_i915_private_t
Date: Mon, 31 Mar 2014 15:28:41 +0300 [thread overview]
Message-ID: <87ioqueeme.fsf@intel.com> (raw)
In-Reply-To: <20140331113509.GB29832@nuc-i3427.alporthouse.com>
On Mon, 31 Mar 2014, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Mon, Mar 31, 2014 at 02:27:22PM +0300, Jani Nikula wrote:
>> There are no longer users of drm_i915_private_t. Drop the typedef. Good
>> riddance.
>
> One last test, we expect i915.ko to be the same before and after.
Any tips for this one? I tried:
$ strip --strip-all --remove-section=.note.gnu.build-id i915.ko
before diffing but it's not sufficient.
BR,
Jani.
> Good riddance,
> Acked-by: Chris Wilson <chris@chris-wislon.co.uk>
^^ ?
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-03-31 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 11:27 [PATCH 0/9] drm/i915: nuke drm_i915_private_t Jani Nikula
2014-03-31 11:27 ` [PATCH 1/9] drm/i915/debugfs: prefer struct drm_i915_private to drm_i915_private_t Jani Nikula
2014-03-31 11:27 ` [PATCH 2/9] drm/i915/dma: " Jani Nikula
2014-03-31 11:27 ` [PATCH 3/9] drm/i915/gem: " Jani Nikula
2014-03-31 11:27 ` [PATCH 4/9] drm/i915/irq: " Jani Nikula
2014-03-31 11:27 ` [PATCH 5/9] drm/i915/display: " Jani Nikula
2014-03-31 11:27 ` [PATCH 6/9] drm/i915/ringbuffer: " Jani Nikula
2014-03-31 11:27 ` [PATCH 7/9] drm/i915/overlay: " Jani Nikula
2014-03-31 11:27 ` [PATCH 8/9] drm/i915: " Jani Nikula
2014-03-31 11:27 ` [PATCH 9/9] drm/i915: drop the typedef for drm_i915_private_t Jani Nikula
2014-03-31 11:35 ` Chris Wilson
2014-03-31 12:28 ` Jani Nikula [this message]
2014-03-31 13:48 ` [PATCH 0/9] drm/i915: nuke drm_i915_private_t 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=87ioqueeme.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--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