Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove unused power well register definitions
Date: Wed, 24 Apr 2013 19:10:37 +0200	[thread overview]
Message-ID: <20130424171037.GZ6169@phenom.ffwll.local> (raw)
In-Reply-To: <1366637999-8425-1-git-send-email-damien.lespiau@intel.com>

On Mon, Apr 22, 2013 at 02:39:59PM +0100, Damien Lespiau wrote:
> Those registers are not used, let's not keep them around for no reason.
> 
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>

Generally if they're not wrong I don't mind some auxialiary register
#defines hanging about. So I'll punt on this one here.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-04-24 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 13:39 [PATCH] drm/i915: Remove unused power well register definitions Damien Lespiau
2013-04-24 17:10 ` 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=20130424171037.GZ6169@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