From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Renninger <trenn@suse.de>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
Len Brown <lenb@kernel.org>,
"Greg Kroah-Hartman" <gregkh@novell.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Linus <torvalds@linux-foundation.org>
Subject: Re: [SUBMIT REQUEST] cpupowerutils for linux-next
Date: Tue, 5 Apr 2011 00:40:11 +1000 [thread overview]
Message-ID: <20110405004011.0628991a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <201104041510.56570.trenn@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
Hi Thomas,
On Mon, 4 Apr 2011 15:10:56 +0200 Thomas Renninger <trenn@suse.de> 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
Has integration of this into the kernel sources been discussed anywhere
generally (like lkml)? Has the work been done to integrate it into the
kernel build system (I am not sure what this involves for the tools
directory). At a first glance, it doesn't need it own copy of the
COPYING file (for example).
I see that you asked Linus about this, but have receibed no reply (on
list).
Code being merged into linux-next should be basically ready for merging
into Linus' tree (apart from integration testing) and you need to be
pretty sure that it will be merged by Linus into the next release (i.e.
2.6.40). In this case that is not such a big issue as the code is
(currently) all in a new directory, so will not interfere with other code.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-04-04 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 13:10 Thomas Renninger
2011-04-04 14:40 ` Stephen Rothwell [this message]
2011-04-04 20:14 ` Thomas Renninger
2011-04-11 3:57 ` Stephen Rothwell
2011-04-11 3:58 ` 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=20110405004011.0628991a.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andreas.herrmann3@amd.com \
--cc=gregkh@novell.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux@dominikbrodowski.net \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®