From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>,
Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-06-03-16-36 uploaded
Date: Thu, 03 Jun 2010 22:23:11 -0400 [thread overview]
Message-ID: <11930.1275618191@localhost> (raw)
In-Reply-To: Your message of "Thu, 03 Jun 2010 16:36:51 PDT." <201006040005.o5405Afw023296@imap1.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Thu, 03 Jun 2010 16:36:51 PDT, akpm@linux-foundation.org said:
> The mm-of-the-moment snapshot 2010-06-03-16-36 has been uploaded to
Not strictly a -mm problemn, but I just noticed it.
In drivers/idle/Kconfig, we see:
Cpuidle Driver for Intel Processors (INTEL_IDLE) [N/m/y/?] (NEW) ?
CONFIG_INTEL_IDLE:
Enable intel_idle, a cpuidle driver that includes knowledge of
native Intel hardware idle features. The acpi_idle driver
can be configured at the same time, in order to handle
processors intel_idle does not support.
I think we wanted a s/acpi_idle/processor_idle/ there?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-06-04 2:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 23:36 mmotm 2010-06-03-16-36 uploaded akpm
2010-06-04 1:14 ` FUJITA Tomonori
2010-06-04 1:34 ` Andrew Morton
2010-06-04 2:16 ` FUJITA Tomonori
2010-06-04 9:32 ` Michael Büsch
2010-06-04 1:41 ` Dave Young
2010-06-04 1:54 ` Andrew Morton
2010-06-04 1:54 ` Andrew Morton
2010-06-04 2:02 ` Dave Young
2010-06-04 2:10 ` Andrew Morton
2010-06-04 2:13 ` Dave Young
2010-06-04 2:13 ` Dave Young
2010-06-04 2:10 ` Andrew Morton
2010-06-04 2:02 ` Dave Young
2010-06-04 1:56 ` Andrew Morton
2010-06-04 1:56 ` Andrew Morton
2010-06-04 1:41 ` Dave Young
2010-06-04 2:23 ` Valdis.Kletnieks [this message]
2010-06-04 16:41 ` [PATCH -mmotm] cciss: fix build for CONFIG_PROC_FS=n Randy Dunlap
2010-06-04 18:07 ` Miller, Mike (OS Dev)
2010-06-05 12:15 ` mmotm 2010-06-03-16-36 uploaded Stephen Rothwell
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=11930.1275618191@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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 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.