All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: stable@vger.kernel.org,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Nick Bowler" <nbowler@draconx.ca>,
	"Jani Nikula" <jani.nikula@intel.com>
Subject: Re: [patch added to the 3.12 stable tree] drm/i915: Restore lost DPLL register write on gen2-4
Date: Thu, 12 Nov 2015 14:10:34 +0100	[thread overview]
Message-ID: <56448FCA.2090300@suse.cz> (raw)
In-Reply-To: <20151111222515.GA15443@charon>

On 11/11/2015, 11:25 PM, Luis Henriques wrote:
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -1379,6 +1379,8 @@ static void i9xx_enable_pll(struct intel_crtc *crtc)
>>  
>>  	I915_WRITE(reg, dpll);
>>  
>> +	I915_WRITE(reg, dpll);
>> +
> 
> I don't think 3.12 actually needs this patch as it does not contain
> commit 1c4e02746147, which deleted the I915_WRITE().

Oh yeah. Now dropped. Thanks!

-- 
js
suse labs

  reply	other threads:[~2015-11-12 13:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 11:56 [patch added to the 3.12 stable tree] spi: fix pointer-integer size mismatch warning Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] drm/nouveau/gem: return only valid domain when there's only one Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] drm/i915: Restore lost DPLL register write on gen2-4 Jiri Slaby
2015-11-11 22:25   ` Luis Henriques
2015-11-12 13:10     ` Jiri Slaby [this message]
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] rbd: require stable pages if message data CRCs are enabled Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] Revert "ARM64: unwind: Fix PC calculation" Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] dm btree: fix leak of bufio-backed block in btree_split_beneath error path Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] xhci: handle no ping response error properly Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] xhci: Add spurious wakeup quirk for LynxPoint-LP controllers Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] xen-blkfront: check for null drvdata in blkback_changed (XenbusStateClosing) Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] module: Fix locking in symbol_put_addr() Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] crypto: api - Only abort operations on fatal signal Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] md/raid1: submit_bio_wait() returns 0 on success Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] md/raid10: " Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] mvsas: Fix NULL pointer dereference in mvs_slot_task_free Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] IB/cm: Fix rb-tree duplicate free and use-after-free Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] serial: 8250_pci: Add support for 16 port Exar boards Jiri Slaby
2015-11-09 11:56 ` [patch added to the 3.12 stable tree] serial: 8250_pci: Add support for 12 " Jiri Slaby

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=56448FCA.2090300@suse.cz \
    --to=jslaby@suse.cz \
    --cc=jani.nikula@intel.com \
    --cc=luis.henriques@canonical.com \
    --cc=nbowler@draconx.ca \
    --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.