public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74751] resume from suspend broken with 3.15-rc1 and rc2 kernels
Date: Tue, 29 Apr 2014 12:30:13 +0000	[thread overview]
Message-ID: <bug-74751-2300-rEkRnOekZv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-74751-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=74751

--- Comment #14 from Tasev Nikola <tasev.stefanoska@skynet.be> ---
Hi,

Here is the patch from the commit that i found with git bisect.
It's a copy paste from gitk for the commit
25f397a429dfa43f22c278d0119a60a343aa568f



---------------------- drivers/gpu/drm/drm_crtc_helper.c ----------------------
index c0f2d62..8108db9 100644
@@ -695,12 +695,13 @@ int drm_crtc_helper_set_config(struct drm_mode_set *set)
                 if (new_encoder == NULL)
                     /* don't break so fail path works correct */
                     fail = 1;
-                break;

                 if (connector->dpms != DRM_MODE_DPMS_ON) {
                     DRM_DEBUG_KMS("connector dpms not on, full mode
switch\n");
                     mode_changed = true;
                 }
+
+                break;
             }
         }

I just changed the break in the code like before the patch and after
recompiling
the 3.15-rc2 the suspend resume work again.
But like i said i'm just an average user so sorry if i did something wrong.
I attached a full copy paste from gitk for the commit
25f397a429dfa43f22c278d0119a60a343aa568f

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-04-29 12:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 16:32 [Bug 74751] New: resume from suspend broken with 3.15-rc1 and rc2 kernels bugzilla-daemon
2014-04-24 16:33 ` [Bug 74751] " bugzilla-daemon
2014-04-24 16:34 ` bugzilla-daemon
2014-04-24 16:34 ` bugzilla-daemon
2014-04-25 13:46 ` bugzilla-daemon
2014-04-25 13:56 ` bugzilla-daemon
2014-04-25 13:58 ` bugzilla-daemon
2014-04-25 18:01 ` bugzilla-daemon
2014-04-25 18:03 ` bugzilla-daemon
2014-04-25 18:04 ` bugzilla-daemon
2014-04-28 14:20 ` bugzilla-daemon
2014-04-29  7:07 ` bugzilla-daemon
2014-04-29  7:08 ` bugzilla-daemon
2014-04-29  7:08 ` bugzilla-daemon
2014-04-29  8:41 ` bugzilla-daemon
2014-04-29 12:30 ` bugzilla-daemon [this message]
2014-04-29 12:31 ` bugzilla-daemon
2014-04-29 12:41 ` bugzilla-daemon
2014-05-05 16:22 ` bugzilla-daemon
2014-05-12 14:25 ` bugzilla-daemon
2014-05-12 14:26 ` bugzilla-daemon
2014-05-13 14:56 ` bugzilla-daemon
2014-05-15 15:17 ` bugzilla-daemon
2014-05-25 18:30 ` bugzilla-daemon
2014-05-27 12:20 ` bugzilla-daemon
2014-05-27 12:22 ` bugzilla-daemon
2014-05-30  8:13 ` bugzilla-daemon
2014-06-01  8:09 ` bugzilla-daemon
2014-06-18 14:59 ` bugzilla-daemon

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=bug-74751-2300-rEkRnOekZv@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@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