All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-acpi@vger.kernel.org, deepthi@linux.vnet.ibm.com,
	shaohua.li@intel.com
Subject: Re: [Resend] X86 cpuidle cleanups V2
Date: Tue, 17 Jan 2012 14:30:29 -0500	[thread overview]
Message-ID: <4F15CC55.70004@kernel.org> (raw)
In-Reply-To: <1326817895-81436-1-git-send-email-trenn@suse.de>

On 01/17/2012 11:31 AM, Thomas Renninger wrote:

> V2: Fix typo: &pr-id
> 
> This is a rebase of some recently posted intel_idle processor_idle
> related patches which needed refreshing, due to recent commits.
> 
> The purpose is to work towards hotplug support for intel_idle.
> It's still missing some logic to boot and online a CPU first
> before intel_idle can initialize the core. But this is the
> essential ground work that is needed first.
> 
> [PATCH 1/3] Revert "intel_idle: disable auto_demotion for hotplugged
> -> because I think it's wrong/unneeded. I commented on the initial
> posting.


#1 done - thanks!

> I tested these patches before I had to rebase them.
> Compile tested only after adjusting, but adjusting the code wasn't that hard.


please fix the checkpatch.pl issues in #2 and #3,
and explain in the check-in comments _why_ the patches
are a good idea.  (less of a need to describe _what_ the patches do,
since the patches themselves are the authority on that:-)

thanks,
-Len Brown, Intel Open Source Technology Center

      parent reply	other threads:[~2012-01-17 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 16:31 [Resend] X86 cpuidle cleanups V2 Thomas Renninger
2012-01-17 16:31 ` [PATCH 1/3] Revert "intel_idle: disable auto_demotion for hotplugged CPUs" Thomas Renninger
2012-01-17 16:31 ` [PATCH 2/3] ACPI processor: Remove unneeded variable passed by acpi_processor_hotadd_init Thomas Renninger
2012-01-17 16:31 ` [PATCH 3/3] intel_idle: Split up and provide per CPU initialization func Thomas Renninger
2012-01-17 19:30 ` Len Brown [this message]

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=4F15CC55.70004@kernel.org \
    --to=lenb@kernel.org \
    --cc=deepthi@linux.vnet.ibm.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=trenn@suse.de \
    /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.