All of lore.kernel.org
 help / color / mirror / Atom feed
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

       reply	other threads:[~2007-03-29 15:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703291304.l2TD4Dd6016401@fire-2.osdl.org>
2007-03-29 15:43 ` Daniel Drake [this message]
     [not found] <bug-8255-3570@http.bugzilla.kernel.org/>
2007-06-29 23:15 ` [Bug 8255] Frequency Scaling not working properly using powernow-k7 bugme-daemon
2007-06-09 15:08 bugme-daemon
  -- strict thread matches above, loose matches on Subject: below --
2007-06-09 12:57 bugme-daemon
2007-06-09 12:56 bugme-daemon
2007-06-09 11:46 bugme-daemon
2007-05-05 14:56 bugme-daemon
2007-05-02 22:55 bugme-daemon
2007-05-02 22:43 bugme-daemon
2007-05-02 22:09 bugme-daemon
2007-05-02 21:55 bugme-daemon
2007-05-02 21:04 bugme-daemon
2007-05-02 18:41 bugme-daemon
2007-05-02 15:26 bugme-daemon
2007-05-02 15:18 bugme-daemon
2007-05-02 10:43 bugme-daemon
2007-05-02  0:31 bugme-daemon
2007-05-01 22:27 bugme-daemon
2007-05-01 21:21 bugme-daemon
2007-05-01 20:56 bugme-daemon
2007-05-01 20:20 bugme-daemon
2007-05-01 20:12 bugme-daemon
2007-05-01 20:11 bugme-daemon
2007-05-01 17:33 bugme-daemon
2007-05-01  9:09 bugme-daemon
2007-04-28 13:56 bugme-daemon
2007-04-28  9:40 bugme-daemon
2007-04-27 13:11 bugme-daemon
2007-04-27 11:53 bugme-daemon
2007-04-27 11:52 bugme-daemon
2007-04-27 11:14 bugme-daemon
2007-04-27 11:13 bugme-daemon
2007-04-27 11:12 bugme-daemon
2007-04-27  1:52 bugme-daemon
2007-04-11 14:52 bugme-daemon
2007-04-01 21:41 bugme-daemon
2007-03-29 15:43 bugme-daemon
2007-03-29 15:38 bugme-daemon
2007-03-29 14:57 bugme-daemon
2007-03-29 13:04 bugme-daemon
2007-03-24 23:48 bugme-daemon
2007-03-24 18:18 bugme-daemon
2007-03-24 18:16 bugme-daemon

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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.