From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/3] drm/i915: drop code duplication in favor of asle interrupt handler
Date: Thu, 25 Apr 2013 15:41:23 +0200 [thread overview]
Message-ID: <20130425134122.GF6169@phenom.ffwll.local> (raw)
In-Reply-To: <20130425130947.GA10193@strange.amr.corp.intel.com>
On Thu, Apr 25, 2013 at 02:09:47PM +0100, Damien Lespiau wrote:
> On Wed, Apr 24, 2013 at 10:18:44PM +0300, Jani Nikula wrote:
> > With the previous work asle and gse interrupt handlers should now be
> > functionally the same. Drop the duplicated code.
> >
> > v2: Drop intel_opregion_gse_intr() also in the !CONFIG_ACPI path. (Damien)
> >
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> To be explicit about it:
>
> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Merged all three patches, thanks.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-04-25 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 12:20 [PATCH 0/3] drm/i915: opregion cleanup Jani Nikula
2013-04-12 12:20 ` [PATCH 1/3] drm/i915: don't pretend we support ASLE ALS, PFIT, or PFMB Jani Nikula
2013-04-12 12:20 ` [PATCH 2/3] drm/i915/opregion: don't pretend we did something when we didn't Jani Nikula
2013-04-12 12:20 ` [PATCH 3/3] drm/i915: drop code duplication in favor of asle interrupt handler Jani Nikula
2013-04-24 18:23 ` Damien Lespiau
[not found] ` <39ef9d9d21a2211333ce011881e240304c3baec1.1366830005.git.jani.nikula@intel.com>
2013-04-24 19:18 ` [PATCH v2 " Jani Nikula
2013-04-24 19:34 ` Jani Nikula
2013-04-25 13:09 ` Damien Lespiau
2013-04-25 13:41 ` Daniel Vetter [this message]
2013-04-24 18:24 ` [PATCH 0/3] drm/i915: opregion cleanup Damien Lespiau
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=20130425134122.GF6169@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/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.