From: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
To: Dave Jones <davej@redhat.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
cpufreq@lists.linux.org.uk
Subject: Re: Suspend to RAM regression tracked down
Date: Sun, 09 Jul 2006 08:55:02 +1000 [thread overview]
Message-ID: <1152399303.14453.29.camel@idefix.homelinux.org> (raw)
In-Reply-To: <20060708062345.GB3356@redhat.com>
> If you're prepared to play around with 'git bisect' a little, it shouldn't
> take that many iterations, as you've already narrowed it down quite a lot.
>
> $ git bisect start drivers/cpufreq/cpufreq_ondemand.c
> $ git bisect bad
> $ git bisect good v2.6.12-rc5
>
> should get you most of the way there.
>
> http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
> has more info.
Could you give me a bit more info, since I've never used git before (I
only downloaded the git snapshots)? Also, if I understand correctly,
cpufreq_ondemand.c is the only file that could cause the problem. Is
that right? Also, is it possible to use an old version of it on a new
kernel?
Jean-Marc
next prev parent reply other threads:[~2006-07-08 22:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 10:47 Jean-Marc Valin
2006-07-02 18:06 ` Jeremy Fitzhardinge
2006-07-02 22:52 ` Jean-Marc Valin
2006-07-03 6:02 ` Jeremy Fitzhardinge
2006-07-03 6:31 ` Jean-Marc Valin
2006-07-03 6:08 ` Jeff Chua
2006-07-07 11:25 ` Jean-Marc Valin
2006-07-07 16:21 ` Dave Jones
2006-07-07 22:48 ` Jean-Marc Valin
2006-07-08 6:23 ` Dave Jones
2006-07-08 22:55 ` Jean-Marc Valin [this message]
2006-07-09 3:21 ` Dave Jones
2006-07-09 5:28 ` Jean-Marc Valin
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=1152399303.14453.29.camel@idefix.homelinux.org \
--to=jean-marc.valin@usherbrooke.ca \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®