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 22:12:26 -0700 [thread overview]
Message-ID: <1c70fd37e4eb876295e0194e2b8725d6@mvista.com> (raw)
In-Reply-To: <20060729004546.GA3917@kroah.com>
Greg,
perhaps I need to back up a bit. I wasn't submitting these patches
for inclusion into Linux. I was presenting them to the people
discussing
how power management might evolve in Linux.
This patch is just a toy prototype to use as a strawman to discuss
how power management infrastructures in Linux might evolve to be more:
a) unified
and
b) simplified for both kernel and user space.
The Documentation/powerop.txt included in the powerop-core.patch
tries to describe what the patch is attempting to do and how it works.
David
On Jul 28, 2006, at 5:45 PM, Greg KH wrote:
> On Fri, Jul 28, 2006 at 05:38:11PM -0700, david singleton wrote:
>>
>> 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?
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>> Here's powerop-core.patch, powerop-cpufreq.patch and
>> powerop-x86-centrino.patch.
>
> Um, no, that's not how kernel patches are submitted. How about one per
> email, with a description of what they do, inline so we can quote them
> in a message (and actually read them in the original message...)
>
> See patches posted here by others as examples of what is expected, and
> see Documentation/SubmittingPatches for more details.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2006-07-29 5:12 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
2006-07-29 0:38 ` david singleton
2006-07-29 0:45 ` Greg KH
2006-07-29 5:12 ` david singleton [this message]
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=1c70fd37e4eb876295e0194e2b8725d6@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