Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Eugeni Dodonov <eugeni@dodonov.net>
Cc: intel-gfx@lists.freedesktop.org,
	Eugeni Dodonov <eugeni.dodonov@intel.com>
Subject: Re: [PATCH 0/5] refactor power management into intel_pm
Date: Tue, 17 Apr 2012 12:23:43 +0200	[thread overview]
Message-ID: <20120417102343.GI4104@phenom.ffwll.local> (raw)
In-Reply-To: <CAC7LmnuPkOHE_t0G4trKaJeKrtnKqohC+kwqO_MyKfz2SH8EZw@mail.gmail.com>

On Tue, Apr 17, 2012 at 06:56:27AM -0300, Eugeni Dodonov wrote:
> On Tue, Apr 17, 2012 at 05:57, Daniel Vetter <daniel@ffwll.ch> wrote:
> 
> > On Mon, Apr 16, 2012 at 10:20:33PM -0300, Eugeni Dodonov wrote:
> > > As Chris Wilson noticed, my previous patch that did the refactoring as
> > one big
> > > patch which moved everything at once was extremely difficult to review
> > and
> > > maintain. So I split the same refactoring into a series of smaller
> > patches,
> > > which move one subsystem at a time.
> >
> > Yeah, diffs are not actually readable, so looks like we have to do this
> > piece-wise.
> 
> 
> Please, tell me that you meant 'diffs are *now* actually readable' with a
> 'not' being a typo instead of 'now' there by a chance...
> 
> Because otherwise I couldn't understand what you meant with piece-wise.
> Should I move each function at a time? :)

Meh, type, diffs are _now_ readable ;-)

> I'll do the intel_pm_init (or intel_init_pm) and send it on top of this
> series. It makes lots of sense and will avoid exposing all those
> platform-specific stuff where we won't need it except for initialization.

Cool, I'll review the entire series in context of that additional patch
then.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-04-17 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  1:20 [PATCH 0/5] refactor power management into intel_pm Eugeni Dodonov
2012-04-17  1:20 ` [PATCH 1/5] drm/i915: move fbc-related functionality into intel_pm module Eugeni Dodonov
2012-04-17  1:20 ` [PATCH 2/5] drm/i915: move watermarks settings " Eugeni Dodonov
2012-04-17  1:20 ` [PATCH 3/5] drm/i915: move drps, rps and rc6-related functions to intel_pm Eugeni Dodonov
2012-04-17  1:20 ` [PATCH 4/5] drm/i915: move emon functionality into intel_pm module Eugeni Dodonov
2012-04-17  1:20 ` [PATCH 5/5] drm/i915: move clock gating " Eugeni Dodonov
2012-04-17  8:57 ` [PATCH 0/5] refactor power management into intel_pm Daniel Vetter
2012-04-17  9:56   ` Eugeni Dodonov
2012-04-17 10:23     ` Daniel Vetter [this message]
2012-04-17 14:04       ` [PATCH 1/1] drm/i915: add generic power management initialization Eugeni Dodonov

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=20120417102343.GI4104@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=eugeni.dodonov@intel.com \
    --cc=eugeni@dodonov.net \
    --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