https://bugzilla.kernel.org/show_bug.cgi?id=100221
--- Comment #54 from Aaron Lu <[email protected]> --- (In reply to Kumar from comment #52) > Hi > > I had tested till : > > [root@localhost linux]# git bisect bad > b5cd43f062717b6c92f93bc0c593764e144ea331 > Bisecting: 45 revisions left to test after this (roughly 6 steps) > [86817ffb492b509b87b20be4a4f1afc74f04dccf] mmc: block: Use mmc_get_ext_csd() > instead of mmc_send_ext_csd() > [root@localhost linux]# > > The above merge was also buggy, as I had compiled, installed the kernel and > tested reboot/shutdown. > > Then I followed along : > > [root@localhost linux]# git bisect start > [root@localhost linux]# git bisect good v3.18 > [root@localhost linux]# git bisect bad > 86817ffb492b509b87b20be4a4f1afc74f04dccf ==> Previous merge. > > The output is as follows : > Bisecting: a merge base must be tested > [206c5f60a3d902bc4b56dab2de3e88de5eb06108] Linux 3.18-rc4 > Now it does not say "xx revisions left to test after this (roughly y steps)" > > > What should I do now? > > Should I continue? According to: https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting:_a_merge_base_must_be_tested You need to tell git if commit 206c5f60a3d902bc4b56dab2de3e88de5eb06108, which is v3.18-rc4 is good or bad. I think you can do that by testing it. -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
