Re: [SUBMIT REQUEST] cpupowerutils for linux-next

[Stephen Rothwell]

Hi Thomas,

On Mon, 4 Apr 2011 15:10:56 +0200 Thomas Renninger <trenn@xxxxxxx> wrote:
>
> this is about the recently announced cpupowerutils project
> based on or say an enhancement of the well know
> cpufrequtils project:
> http://www.spinics.net/lists/cpufreq/msg02137.html
> 
> It's basically cpufrequtils with some cpuidle info additions
> and the Intel only turbostat tool merged into it in a way
> that it can easily get extended for other HW (and got extended
> with some AMD facilities).
> 
> As there is tools/power/x86 for some time, it would be very
> convenient to get cpupowerutils merged into linux-next (for now)
> into the tools/power/cpupower directory:
> Most of it is directly based on the cpufreq/cpuidle kernel
> subsystem and the output gathered by it should be attached
> to any CPU frequency/idle related kernel bug.
> 
> Dominik was so kind to add the stuff to his pcmcia git tree
> as cpupowerutils branch.
> Therefore, this can easily be added by pulling from:
> git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git cpupowerutils

OK, I have added this tree starting tomorrow.

> Stephen: I added lkml, linux-pm lists and kernel people I know
> working in this area. Please tell me if you can/will just
> pull this or whatever you need to make it happen.

This maens that I will fetch from that tree every day and merge it into
linux-next.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@xxxxxxxxxxxxxxxx

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Attachment: pgp00000.pgp
Description: PGP signature