From: Len Brown <lenb@kernel.org>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: linux-acpi@vger.kernel.org, abelay@novell.com
Subject: Re: [PATCH] Retain old acpi policy for !CONFIG_CPU_IDLE
Date: Fri, 21 Sep 2007 23:00:55 -0400 [thread overview]
Message-ID: <200709212300.56116.lenb@kernel.org> (raw)
In-Reply-To: <20070913204005.GB1183@linux-os.sc.intel.com>
I couldn't get this patch to apply.
the current cpuidle branch is rooted at 2.6.22.
I'd like to see a patch on top of that branch
that restores as much of processor_idle.c as possible
to the state in 2.6.22.
ie. a diff of 2.6.22 and cpuidle processor_idle.c
should be as small as possible -- and it is okay
to use a bunch of CONFIG_CPU_IDLE ifdefs to keep things simple.
I can take care of merging that with the other changes
to processor_idle.c that have come along in 2.6.23.
thanks,
-Len
On Thursday 13 September 2007 16:40, Venki Pallipadi wrote:
>
> Retain the old policy in processor_idle, so that when CPU_IDLE is not
> configured, old C-state policy will still be used. This provides a
> clean gradual migration path from old acpi policy to new cpuidle
> based policy.
>
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>
> Index: linux-2.6.23-rc6/drivers/acpi/processor_idle.c
> ===================================================================
> --- linux-2.6.23-rc6.orig/drivers/acpi/processor_idle.c
> +++ linux-2.6.23-rc6/drivers/acpi/processor_idle.c
> @@ -65,14 +65,20 @@ ACPI_MODULE_NAME("processor_idle");
next prev parent reply other threads:[~2007-09-22 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 20:40 [PATCH] Retain old acpi policy for !CONFIG_CPU_IDLE Venki Pallipadi
2007-09-22 3:00 ` Len Brown [this message]
2007-09-25 22:13 ` Len Brown
2007-09-26 6:16 ` [PATCH] cpuidle: reduce diff size Len Brown
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=200709212300.56116.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=abelay@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/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.