From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: cpufrequtils do_install issue
Date: Tue, 03 Apr 2012 19:30:14 +0100 [thread overview]
Message-ID: <4F7B41B6.2080605@communistcode.co.uk> (raw)
In-Reply-To: <CAMKF1soCWnGaZJ0iv=k7MHMxYgyyDeCZQ3kesxvOh4GFYGvcdA@mail.gmail.com>
On 03/04/2012 14:42, Khem Raj wrote:
> On Tue, Apr 3, 2012 at 12:58 AM, Jack Mitchell<ml@communistcode.co.uk> wrote:
>> For the record the new kid on the block in this area is called 'cpupower' it
>> builds on cpufrequtils and brings it up to date (last cpufrequtils commit
>> was sometime in 2009 if I remember correctly!) and is much better. If anyone
>> is attempting to use cpufrequtils I would recommend checking it out instead.
> if you have cpupower recipes for OE I would encourage you to contribute
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Unfortunately it was a package that was pulled in as a dependency so I
wasn't interested in using it (it wasn't going in the image), however I
believe I will be contributing my first package soon in the form of a
webserver I use so keep eyes peeled for an RFC soon :)
Actually, on that note what constitutes getting a package into OE, or is
it just submit and if people think it's useful in it goes?
Cheers,
Jack.
prev parent reply other threads:[~2012-04-03 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 13:45 cpufrequtils do_install issue Jack Mitchell
2012-03-15 10:35 ` Jack Mitchell
2012-04-02 16:56 ` Khem Raj
2012-04-03 7:58 ` Jack Mitchell
2012-04-03 13:42 ` Khem Raj
2012-04-03 18:30 ` Jack Mitchell [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=4F7B41B6.2080605@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.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