linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Voluspa <lista1@telia.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.15-rc6
Date: Wed, 21 Dec 2005 14:51:57 +0100	[thread overview]
Message-ID: <20051221145157.72887fa4.lista1@telia.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0512202131000.4827@g5.osdl.org>

On Tue, 20 Dec 2005 21:33:28 -0800 (PST) Linus Torvalds wrote:
[...]
> But it might make sense to open a bugzilla entry so that it doesn't get 
> lost.

http://bugzilla.kernel.org/show_bug.cgi?id=5767

For anyone stumbling into this problem, lacking git experience, here's
a 1/10-revert patch that gives me back the former functionality. It
behaves exactly as in 2.6.14 with regards to C1 usage and thermal_zone
temperatures etc.

diff -Nur linux-2.6.15-rc6-clean/drivers/acpi/processor_idle.c linux-2.6.15-rc6-c1fix/drivers/acpi/processor_idle.c
--- linux-2.6.15-rc6-clean/drivers/acpi/processor_idle.c	2005-12-21 13:29:12.000000000 +0100
+++ linux-2.6.15-rc6-c1fix/drivers/acpi/processor_idle.c	2005-12-21 13:39:04.000000000 +0100
@@ -893,7 +893,7 @@
 	for (i = 1; i < ACPI_PROCESSOR_MAX_POWER; i++) {
 		if (pr->power.states[i].valid) {
 			pr->power.count = i;
-			if (pr->power.states[i].type >= ACPI_STATE_C2)
+			if (pr->power.states[i].type >= ACPI_STATE_C1)
 				pr->flags.power = 1;
 		}
 	}

Mvh
Mats Johannesson
--

  parent reply	other threads:[~2005-12-21 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21  4:21 Linux 2.6.15-rc6 Voluspa
2005-12-21  5:33 ` Linus Torvalds
2005-12-21  5:45   ` Voluspa
2005-12-21 13:51   ` Voluspa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-19  8:50 Voluspa
2005-12-19  0:47 Linus Torvalds
2005-12-19  1:30 ` Diego Calleja
2005-12-19  5:41   ` Willy Tarreau

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=20051221145157.72887fa4.lista1@telia.com \
    --to=lista1@telia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).