public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: david singleton <dsingleton@mvista.com>
To: Greg KH <greg@kroah.com>
Cc: David Singleton <daviado@gmail.com>, linux-pm@lists.osdl.org
Subject: Re: PowerOp Design and working patch
Date: Fri, 28 Jul 2006 17:26:34 -0700	[thread overview]
Message-ID: <f86e151863675b397a533c61c0b030f1@mvista.com> (raw)
In-Reply-To: <20060728233837.GG2140@kroah.com>


On Jul 28, 2006, at 4:38 PM, Greg KH wrote:

> On Fri, Jul 28, 2006 at 03:31:41PM -0700, david singleton wrote:
>> Here is a patch that implements a version of the PowerOp concept.
>
> Any chance of breaking this up into logical patches that do one thing 
> at
> a time so it can be reviewed better?

Sure.  It was so small I just put them all together:

linux-2.6.17> quilt files
kernel/power/main.c
include/linux/pm.h
kernel/power/power.h
Makefile
arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c
drivers/cpufreq/cpufreq.c
include/linux/cpufreq.h
Documentation/power/powerop.txt


I'll make a core patch and an x86-centrino patch.

David
>
> thanks,
>
> greg k-h

  reply	other threads:[~2006-07-29  0:26 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-28 22:31 PowerOp Design and working patch david singleton
2006-07-28 23:38 ` Greg KH
2006-07-29  0:26   ` david singleton [this message]
2006-07-29  0:38   ` david singleton
2006-07-29  0:45     ` Greg KH
2006-07-29  5:12       ` david singleton
2006-07-29 19:07         ` Eugeny S. Mints
2006-07-30  4:43           ` david singleton
2006-07-30 11:02             ` Vitaly Wool
2006-08-01  0:59               ` david singleton
2006-08-01 10:09                 ` Matthew Locke
2006-08-01 10:22                   ` Matthew Locke
2006-08-01 18:31                   ` david singleton
2006-08-01 18:52                     ` Tim Bird
2006-08-01 18:59                       ` david singleton
2006-08-01 19:17                         ` Vitaly Wool
2006-08-01 19:28                       ` Vitaly Wool
2006-08-06 22:11                       ` Pavel Machek
2006-08-07 10:34                         ` Igor Stoppa
2006-08-07 19:45                         ` Tim Bird
2006-08-08 10:07                           ` Pavel Machek
2006-08-08 11:12                             ` Igor Stoppa
2006-08-08 11:33                               ` Pavel Machek
2006-08-08 16:43                                 ` Tim Bird
2006-08-01 12:23                 ` Vitaly Wool
2006-08-01 18:25                   ` Tim Bird
2006-08-01 18:02               ` Tim Bird
2006-08-06 22:05             ` Pavel Machek
2006-08-07  3:52               ` david singleton
2006-08-07  4:17                 ` Greg KH
2006-08-07  4:32                   ` Vitaly Wool
2006-07-29 22:09         ` Greg KH
2006-08-01  0:36           ` david singleton
2006-08-01  1:27           ` david singleton
2006-08-07 22:06     ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-08-01 10:09 Matthew Locke
2006-08-07 14:12 Scott E. Preece
2006-08-07 16:58 ` Greg KH
2006-08-08 13:44 Scott E. Preece
2006-08-08 13:52 ` Pavel Machek
2006-08-08 15:53   ` Matthew Locke
2006-08-08 16:03     ` Matthew Locke
2006-08-08 18:10   ` Igor Stoppa
2006-08-08 13:54 Scott E. Preece
2006-08-08 16:49 ` Tim Bird

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=f86e151863675b397a533c61c0b030f1@mvista.com \
    --to=dsingleton@mvista.com \
    --cc=daviado@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-pm@lists.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