From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Removal of some unused defines
Date: Tue, 20 Aug 2013 07:23:48 +0200 [thread overview]
Message-ID: <20130820052348.GP776@phenom.ffwll.local> (raw)
In-Reply-To: <1376937123-27706-1-git-send-email-damien.lespiau@intel.com>
On Mon, Aug 19, 2013 at 07:31:59PM +0100, Damien Lespiau wrote:
> A small series to remove a few of those. I guess it's debatable if the
> i915_READ_* for ring registers should be removed or the code ported to always
> use those macros.
Entire series merged to dinq, thanks for the patches.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-08-20 5:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 18:31 Removal of some unused defines Damien Lespiau
2013-08-19 18:32 ` [PATCH 1/4] drm/i915: Remove DSPARB_HWCONTROL() Damien Lespiau
2013-08-19 18:32 ` [PATCH 2/4] drm/i915: Remove HAS_PIPE_CONTROL() Damien Lespiau
2013-08-19 18:32 ` [PATCH 3/4] drm: Remove IS_IRONLAKE_D() Damien Lespiau
2013-08-19 18:32 ` [PATCH 4/4] drm/i915: Remove I915_READ_{NOPID, SYNC_0, SYNC_1})() Damien Lespiau
2013-08-20 5:23 ` Daniel Vetter [this message]
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=20130820052348.GP776@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=damien.lespiau@intel.com \
--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