From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix up some stray to_i915(dev) after a recent merge
Date: Thu, 28 Jul 2016 14:01:21 +0200 [thread overview]
Message-ID: <20160728120121.GO6232@phenom.ffwll.local> (raw)
In-Reply-To: <20160728063046.GA7626@nuc-i3427.alporthouse.com>
On Thu, Jul 28, 2016 at 07:30:46AM +0100, Chris Wilson wrote:
> On Thu, Jul 28, 2016 at 09:11:31AM +0300, Joonas Lahtinen wrote:
> > On ke, 2016-07-27 at 19:32 +0100, Chris Wilson wrote:
> > > The merge conflict resolution caused some dev->dev_private to return
> > > from the dead. Kill them with to_i915().
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> >
> > > ---
> > > drivers/gpu/drm/i915/i915_sysfs.c | 2 +-
> > > drivers/gpu/drm/i915/intel_pm.c | 4 ++--
> > > 2 files changed, 3 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_sysfs.c b/drivers/gpu/drm/i915/i915_sysfs.c
> > > index d47281b4b1c1..f1ffde7f7c0b 100644
> > > --- a/drivers/gpu/drm/i915/i915_sysfs.c
> > > +++ b/drivers/gpu/drm/i915/i915_sysfs.c
> > > @@ -323,7 +323,7 @@ static ssize_t gt_boost_freq_mhz_store(struct device *kdev,
> > > {
> > > struct drm_minor *minor = dev_to_drm_minor(kdev);
> > > struct drm_device *dev = minor->dev;
> > > - struct drm_i915_private *dev_priv = dev->dev_private;
> > > + struct drm_i915_private *dev_priv = to_i915(dev);
> > > u32 val;
> > > ssize_t ret;
> > >
> > > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > > index a807e1045b1d..94f41e72cf52 100644
> > > --- a/drivers/gpu/drm/i915/intel_pm.c
> > > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > > @@ -57,7 +57,7 @@
> > >
> > > static void gen9_init_clock_gating(struct drm_device *dev)
> > > {
> > > - struct drm_i915_private *dev_priv = dev->dev_private;
> > > + struct drm_i915_private *dev_priv = to_i915(dev);
> > >
> > > /* See Bspec note for PSR2_CTL bit 31, Wa#828:skl,bxt,kbl */
> > > I915_WRITE(CHICKEN_PAR1_1,
> > > @@ -7056,7 +7056,7 @@ static void kabylake_init_clock_gating(struct drm_device *dev)
> > >
> > > static void skylake_init_clock_gating(struct drm_device *dev)
> > > {
> > > - struct drm_i915_private *dev_priv = dev->dev_private;
> > > + struct drm_i915_private *dev_priv = to_i915(dev);
> > >
> > > gen9_init_clock_gating(dev);
> > >
>
> Hmm, Daniel these are actually somewhere between drm-intel-next-queued
> and drm-intel-nightly. Probably simpler if we just wait for the eventual
> merge and fix up any residual afterwards.
Yup, I plan to backmerge drm-next as soon as Dave finalizes the 4.8 pull
request. We need to sync up a bit ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-07-28 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 18:32 [PATCH] drm/i915: Fix up some stray to_i915(dev) after a recent merge Chris Wilson
2016-07-28 5:39 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-07-28 6:11 ` [PATCH] " Joonas Lahtinen
2016-07-28 6:30 ` Chris Wilson
2016-07-28 12:01 ` 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=20160728120121.GO6232@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.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.