From: Len Brown <lenb@kernel.org>
To: linux-pm@lists.linux-foundation.org
Subject: idle patches for 2.6.38-merge
Date: Wed, 12 Jan 2011 22:39:50 -0500 [thread overview]
Message-ID: <1294890002-6274-1-git-send-email-lenb@kernel.org> (raw)
Here is my queue of idle patches for 2.6.38.
Please speak up if you see troubles with any of them.
thanks
Len Brown, Intel Open Source Technology Center
next reply other threads:[~2011-01-13 3:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 3:39 Len Brown [this message]
2011-01-13 3:39 ` [PATCH 01/12] intel_idle: update Sandy Bridge core C-state residency targets Len Brown
2011-01-13 3:39 ` [PATCH 02/12] cpuidle: Make cpuidle_enable_device() call poll_idle_init() Len Brown
2011-01-13 3:39 ` [PATCH 03/12] ACPI, intel_idle: Cleanup idle= internal variables Len Brown
2011-01-13 3:39 ` [PATCH 04/12] cpuidle: Rename X86 specific idle poll state[0] from C0 to POLL Len Brown
2011-01-13 3:39 ` [PATCH 05/12] ACPI: processor_idle: delete use of NOP CPUIDLE_FLAGs Len Brown
2011-01-13 3:39 ` [PATCH 06/12] cpuidle: delete NOP CPUIDLE_FLAG_POLL Len Brown
2011-01-13 3:39 ` [PATCH 07/12] SH, cpuidle: delete use of NOP CPUIDLE_FLAGS_SHALLOW Len Brown
2011-01-13 3:39 ` [PATCH 08/12] cpuidle: delete unused CPUIDLE_FLAG_SHALLOW, BALANCED, DEEP definitions Len Brown
2011-01-13 3:39 ` [PATCH 09/12] cpuidle: CPUIDLE_FLAG_TLB_FLUSHED is specific to intel_idle Len Brown
2011-01-13 3:40 ` [PATCH 10/12] cpuidle: CPUIDLE_FLAG_CHECK_BM is omap3_idle specific Len Brown
2011-01-13 3:40 ` [PATCH 11/12] intel_idle: open broadcast clock event Len Brown
2011-01-13 3:40 ` [PATCH 12/12] cpuidle/x86/perf: fix power:cpu_idle double end events and throw cpu_idle events from the cpuidle layer 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=1294890002-6274-1-git-send-email-lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-pm@lists.linux-foundation.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