Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH] stress-ng: add 0.05.09
Date: Wed, 27 Jan 2016 14:16:14 -0500	[thread overview]
Message-ID: <20160127191614.GH1652@denix.org> (raw)
In-Reply-To: <20160126142023.GE1652@denix.org>

On Tue, Jan 26, 2016 at 09:20:23AM -0500, Denys Dmytriyenko wrote:
> On Tue, Jan 26, 2016 at 11:24:43AM +0000, Burton, Ross wrote:
> > On 26 January 2016 at 03:34, Denys Dmytriyenko <denis@denix.org> wrote:
> > 
> > > A clean room re-implementation and extension of the original stress tool.
> > >
> > 
> > What's the rationale for adding this to oe-core over another layer?
> 
> None, besides the original stress is in oe-core. What other layer would you 
> suggest?

Ross,

Care do make your own suggestion? Do you think meta-oe would be a better fit? 
Are there any other considerations, since stress-ng is a replacement of the 
original stress and it was added to oe-core? Thanks.

-- 
Denys


  parent reply	other threads:[~2016-01-27 19:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  3:34 [PATCH] stress-ng: add 0.05.09 Denys Dmytriyenko
2016-01-26  4:36 ` Robert Yang
2016-01-26  5:04   ` Denys Dmytriyenko
2016-01-28  6:46   ` Mike Looijmans
2016-01-26 11:24 ` Burton, Ross
2016-01-26 14:20   ` Denys Dmytriyenko
2016-01-26 16:02     ` Otavio Salvador
2016-01-26 16:16       ` Maxin B. John
2016-01-27 19:16     ` Denys Dmytriyenko [this message]
2016-01-27 19:28       ` Khem Raj
2016-01-27 19:37         ` Paul Eggleton
2016-01-27 19:48           ` Khem Raj
2016-01-26 16:01 ` Otavio Salvador
2016-01-26 16:14   ` Denys Dmytriyenko
2016-01-26 16:18     ` Otavio Salvador
2016-01-27 19:08       ` Denys Dmytriyenko

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=20160127191614.GH1652@denix.org \
    --to=denis@denix.org \
    --cc=denys@ti.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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