All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101391] Lockup after resume (kernel BUG at include/drm/drm_mm.h:145!)
Date: Thu, 06 Aug 2015 02:12:39 +0000	[thread overview]
Message-ID: <bug-101391-2300-trtW2LOKPr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-101391-2300@https.bugzilla.kernel.org/>

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

--- Comment #4 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Michael Long from comment #3)
> Bisecting: 12 revisions left to test after this (roughly 4 steps)
> error: Your local changes to the following files would be overwritten by
> checkout:

You need to remove your local modifications. Save them first if you still need
them. If you need the local modifications for bisecting, you can apply them
again after git bisect checked out the next commit to test.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-08-06  2:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12  9:12 [Bug 101391] New: Lockup after resume (kernel BUG at include/drm/drm_mm.h:145!) bugzilla-daemon
2015-07-13  1:58 ` [Bug 101391] " bugzilla-daemon
2015-07-13 18:42 ` bugzilla-daemon
2015-08-05 17:17 ` bugzilla-daemon
2015-08-06  2:12 ` bugzilla-daemon [this message]
2015-08-12  9:01 ` bugzilla-daemon
2015-08-12  9:12 ` bugzilla-daemon
2015-09-26 16:37 ` 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-101391-2300-trtW2LOKPr@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 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.