From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Renato S. Yamane" <yamane@diamondcut.com.br>
Cc: "Pavel Machek" <pavel@suse.cz>,
linux-kernel@vger.kernel.org,
power-management_other@kernel-bugs.osdl.org
Subject: Re: [Bug 10797] Battery is drained after poweroff
Date: Sat, 18 Oct 2008 22:12:33 +0200 [thread overview]
Message-ID: <200810182212.34290.rjw@sisk.pl> (raw)
In-Reply-To: <4199.200.180.173.111.1224358421.mandic:mail - neo@webmail.mandic.com.br>
On Saturday, 18 of October 2008, Renato S. Yamane wrote:
> Rafael J. Wysocki wrote:
> > It follows from your reports that the problem is present in 2.6.22, although
> > it wasn't present in 2.6.21. If that's correct, you can do the following:
> > 1) Clone the Linus' -git repository (if you have a copy already, you can use
> > it)
> > 2) Go to the directory containing your copy of the Linus' repo and do
> > # git bisect start
> > # git bisect good v2.6.21
> > # git bisect bad v2.6.22
> > 3) Wait for git to select a commit to test, build the kernel and test it.
>
> $ git bisect good v2.6.22
> $ git bisect bad v2.6.23
> Bisecting: *3554* revisions left to test after this
>
> This means that I need compile kernel *3554* times?
No, you'll need to compile it approximately log_2(3554) times which is not
that bad. :-)
Thanks,
Rafael
next parent reply other threads:[~2008-10-18 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4199.200.180.173.111.1224358421.mandic:mail - neo@webmail.mandic.com.br>
2008-10-18 20:12 ` Rafael J. Wysocki [this message]
[not found] <6868482180440484264@unknownmsgid>
2008-10-25 23:42 ` Justin Mattock
[not found] <20494.201.3.158.14.1223417777.mandic:mail - neo@webmail.mandic.com.br>
2008-10-07 22:28 ` Pavel Machek
2008-10-07 22:35 ` Rafael J. Wysocki
2008-10-06 11:16 Renato S. Yamane
2008-10-07 13:42 ` Pavel Machek
2008-10-07 16:06 ` Renato S. Yamane
2008-10-07 19:00 ` Pavel Machek
2008-10-07 19:12 ` Kok, Auke
2008-10-07 19:30 ` Rafael J. Wysocki
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=200810182212.34290.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=power-management_other@kernel-bugs.osdl.org \
--cc=yamane@diamondcut.com.br \
/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
all inboxes | Powered by JetHome®