From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fix up ilk rc6 disabling confusion
Date: Mon, 2 Jul 2012 18:49:43 +0200 [thread overview]
Message-ID: <20120702164943.GD5064@phenom.ffwll.local> (raw)
In-Reply-To: <20120702084400.478288aa@bwidawsk.net>
On Mon, Jul 02, 2012 at 08:44:00AM -0700, Ben Widawsky wrote:
> On Sun, 1 Jul 2012 12:48:59 +0200
> Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > Hm, I don't see the comment you're talking about ... Neither
> > ironlake_disable_rc6 nor ironlake_teardown_rc6 nor any of the callers
> > have one. Or am I totally missing your point?
> > -Daniel
> >
>
> iirc in the past, disabling rc6 mean disable, and destroy the object.
> Now it simply means disable. If that's the case, really just a comment
> in the commit would have made me happy. If it's not the case, ignore.
I think in the past disabl_rc6 meant disable&destroy on ilk, but disable
but not destroy on snb. I'll add a comment to the commit message to
mention that.
>
> > >
> > >>
> > >> Also properly mark ironlake_enable_rc6 as static and kill the un-used
> > >> declaration in i915_drv.h.
> > >>
> > >> Cc: Ben Widawsky <ben@bwidawsk.net>
> > >> Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
>
> Again,
> Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
Thanks, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-07-02 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 21:32 [PATCH] drm/i915: fix up ilk rc6 disabling confusion Daniel Vetter
2012-06-29 23:36 ` Eugeni Dodonov
2012-06-30 5:51 ` Daniel Vetter
2012-07-01 3:04 ` Ben Widawsky
2012-07-01 10:48 ` Daniel Vetter
2012-07-02 15:44 ` Ben Widawsky
2012-07-02 16:49 ` Daniel Vetter [this message]
2012-07-04 7:38 ` 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=20120702164943.GD5064@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--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;
as well as URLs for NNTP newsgroup(s).