All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: ville.syrjala@linux.intel.com, intel-gfx@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Mika Kahola <mika.kahola@intel.com>,
	bruno.pagani@ens-lyon.org,
	Daniel J Blueman <daniel.blueman@gmail.com>,
	Joseph Yasi <joe.yasi@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things
Date: Fri, 28 Oct 2016 23:05:48 +0200	[thread overview]
Message-ID: <1477688748.2167.17.camel@tiscali.nl> (raw)
In-Reply-To: <1477673960-3274-1-git-send-email-ville.syrjala@linux.intel.com>

On Fri, 2016-10-28 at 19:59 +0300, ville.syrjala@linux.intel.com wrote:
> Fixes: 1a617b77658e ("drm/i915: Keep track of the cdclk as if all crtc's were active.")

Obviously, I'm pretty happy with this patch. One question though: this
fixes a commit that shipped in v4.6. Do you have any idea why this
issue apparently never surfaced before v4.8?

Thanks,


Paul Bolle

WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: ville.syrjala@linux.intel.com, intel-gfx@lists.freedesktop.org
Cc: bruno.pagani@ens-lyon.org,
	Daniel J Blueman <daniel.blueman@gmail.com>,
	stable@vger.kernel.org, Joseph Yasi <joe.yasi@gmail.com>
Subject: Re: [PATCH] drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things
Date: Fri, 28 Oct 2016 23:05:48 +0200	[thread overview]
Message-ID: <1477688748.2167.17.camel@tiscali.nl> (raw)
In-Reply-To: <1477673960-3274-1-git-send-email-ville.syrjala@linux.intel.com>

On Fri, 2016-10-28 at 19:59 +0300, ville.syrjala@linux.intel.com wrote:
> Fixes: 1a617b77658e ("drm/i915: Keep track of the cdclk as if all crtc's were active.")

Obviously, I'm pretty happy with this patch. One question though: this
fixes a commit that shipped in v4.6. Do you have any idea why this
issue apparently never surfaced before v4.8?

Thanks,


Paul Bolle
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-10-28 21:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 16:59 [PATCH] drm/i915: Fix cdclk vs. dev_cdclk mess when not recomputing things ville.syrjala
2016-10-28 16:59 ` ville.syrjala
2016-10-28 17:15 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-10-28 21:05 ` Paul Bolle [this message]
2016-10-28 21:05   ` [PATCH] " Paul Bolle
2016-10-28 21:30   ` Ville Syrjälä
2016-10-28 21:30     ` Ville Syrjälä
2016-10-28 21:38     ` Paul Bolle
2016-10-28 21:38       ` Paul Bolle
2016-10-28 22:01       ` Ville Syrjälä
2016-10-28 22:01         ` Ville Syrjälä
2016-11-01  8:57 ` Maarten Lankhorst
2016-11-01  8:57   ` Maarten Lankhorst
2016-11-01  9:07   ` Paul Bolle
2016-11-01 12:41     ` Ville Syrjälä
2016-11-01 12:41       ` Ville Syrjälä
2016-11-01 12:40   ` Ville Syrjälä
2016-11-01 12:40     ` Ville Syrjälä
2016-11-01 12:53     ` Ville Syrjälä
2016-11-01 12:53       ` Ville Syrjälä

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=1477688748.2167.17.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=bruno.pagani@ens-lyon.org \
    --cc=daniel.blueman@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joe.yasi@gmail.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mika.kahola@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@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.