From: Daniel Drake <dsd@gentoo.org>
To: Dave Jones <davej@redhat.com>
Cc: bugme-daemon@bugzilla.kernel.org,
linux list <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [Bug 8255] Frequency Scaling not working properly using powernow-k7
Date: Thu, 29 Mar 2007 11:43:17 -0400 [thread overview]
Message-ID: <460BDE95.90204@gentoo.org> (raw)
In-Reply-To: <200703291304.l2TD4Dd6016401@fire-2.osdl.org>
Dave,
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8255
> Okay. I tracked down the problem with git. Here is what is the submission that
> causes the problem:
>
> solaris linux-git # git bisect good
> 0916bd3ebb7cefdd0f432e8491abe24f4b5a101e is first bad commit
> commit 0916bd3ebb7cefdd0f432e8491abe24f4b5a101e
> Author: Dave Jones <davej@redhat.com>
> Date: Wed Nov 22 20:42:01 2006 -0500
>
> [PATCH] Correct bound checking from the value returned from _PPC method.
The above commit seems to be the culprit behind this 2.6.19 regression,
which is still present as of 2.6.21-rc3 (so it's not the earlier issue
found by Ingo). Any ideas?
Thanks,
Daniel
parent reply other threads:[~2007-03-29 15:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200703291304.l2TD4Dd6016401@fire-2.osdl.org>]
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=460BDE95.90204@gentoo.org \
--to=dsd@gentoo.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davej@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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