From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 66963] Rv6xx dpm problems Date: Tue, 07 Jul 2015 22:40:36 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0489358448==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 5AC876E5D7 for ; Tue, 7 Jul 2015 15:40:37 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0489358448== Content-Type: multipart/alternative; boundary="1436308837.a0b86F8.15984"; charset="UTF-8" --1436308837.a0b86F8.15984 Date: Tue, 7 Jul 2015 22:40:37 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=66963 --- Comment #283 from Alex Deucher --- (In reply to Kajzer from comment #282) > I'm running now on kernel compiled with first method, if previous bisect was > indeed done right I don't expect dpm freeze. > > Anyway, thanks for the second method, if I understood you correctly, > basically I can test if Michel's commit is bad or not by running : > $ git bisect reset You only need this if you had previously started a bisect (git bisect start). > $ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13 that will create a new branch named testing. If you already did that, you will need to delete the existing testing branch first before you create another branch with the same name. So either delete the branch when you are done with it (git branch -D testing) or create a new branch name (git branch -b testing2 02376d8282b88f07d0716da6155094c8760b1a13). -- You are receiving this mail because: You are the assignee for the bug. --1436308837.a0b86F8.15984 Date: Tue, 7 Jul 2015 22:40:37 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 283 on bug 66963 from 
(In reply to Kajzer from comment #282)
> I'm running now on kernel compiled with first method, if previous bisect was
> indeed done right I don't expect dpm freeze.
> 
> Anyway, thanks for the second method, if I understood you correctly,
> basically I can test if Michel's commit is bad or not by running :
> $ git bisect reset

You only need this if you had previously started a bisect (git bisect start).

> $ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13

that will create a new branch named testing.  If you already did that, you will
need to delete the existing testing branch first before you create another
branch with the same name.  So either delete the branch when you are done with
it (git branch -D testing) or create a new branch name (git branch -b testing2
02376d8282b88f07d0716da6155094c8760b1a13).

You are receiving this mail because:
  • You are the assignee for the bug.
--1436308837.a0b86F8.15984-- --===============0489358448== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0489358448==--