From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] linaro-pm-qa-utils: Add power management test utils
Date: Wed, 19 Mar 2014 18:31:47 -0600 [thread overview]
Message-ID: <532A36F3.2090800@mlbassoc.com> (raw)
In-Reply-To: <CAP9ODKqhnScZ+__098Q7OS53WrkkASfrfSxdkGt3OeozZ=2yJA@mail.gmail.com>
On 2014-03-19 16:38, Otavio Salvador wrote:
> On Tue, Mar 18, 2014 at 9:56 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Tue, 2014-03-18 at 13:29 +0100, Koen Kooi wrote:
>>> Op 18 mrt. 2014, om 12:56 heeft Chase Maupin <Chase.Maupin@ti.com> het volgende geschreven:
>>>
>>>> * The power management test utilities from Linaro can be used
>>>> to test multiple PM features such as cpufreq, cpuidle, thermal
>>>> control and suspend operations.
>>>> * These utilities are not platform specific and can be used by
>>>> a broader base of users.
>>>
>>> PN should me 'pm-qa' or 'pm-qa-utils'.
>>
>> Agreed.
>>
>>> And it would fit better in meta-oe since it's not 'core' enough for oe-core.
>>
>> I'm open to discussion on that. Certainly if there is just one user,
>> meta-oe would be appropriate. If these are generically useful and the
>> plan is we integrate these into the larger automated test picture,
>> oe-core may make sense.
>>
>> So if there a bigger picture plan here? Would these make sense in the
>> broader picture?
>
> I prefer if this is done in meta-oe first and we move to oe-core when
> needed. For now it is at very beginning so we still does not know what
> will be the real final picture of t.
>
What are you afraid of? Putting this in OE-core _may_ make sense
if it serves a larger community, but having it there will not be
destabilizing, so why not?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-20 0:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 11:56 [PATCH 1/2] linaro-pm-qa-utils: Add power management test utils Chase Maupin
2014-03-18 11:56 ` [PATCH 2/2] mmc-utils: Add user space mmc utilities for eMMC Chase Maupin
2014-03-20 20:10 ` Otavio Salvador
2014-03-18 12:29 ` [PATCH 1/2] linaro-pm-qa-utils: Add power management test utils Koen Kooi
2014-03-18 12:56 ` Richard Purdie
2014-03-18 13:40 ` Maupin, Chase
2014-03-19 22:38 ` Otavio Salvador
2014-03-20 0:31 ` Gary Thomas [this message]
2014-03-20 0:45 ` Khem Raj
2014-03-20 11:57 ` Otavio Salvador
2014-03-20 12:23 ` Maupin, Chase
2014-03-20 13:15 ` Otavio Salvador
2014-03-20 14:27 ` Maupin, Chase
2014-03-20 20:41 ` Otavio Salvador
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=532A36F3.2090800@mlbassoc.com \
--to=gary@mlbassoc.com \
--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