From: Denys Dmytriyenko <denys@ti.com>
To: Karthik Ramanan <a0393906@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [master] weston: Add SoC performance monitoring utilities
Date: Wed, 15 Mar 2017 11:26:10 -0400 [thread overview]
Message-ID: <20170315152610.GT578@edge> (raw)
In-Reply-To: <58C8A9B2.40606@ti.com>
On Wed, Mar 15, 2017 at 08:10:50AM +0530, Karthik Ramanan wrote:
> Denys,
>
> Yes this is for morty.
> May be I missed a notification on this, I'm thinking morty=master?
> Should I mention morty explicitly?
>
>
> On 15-Mar-17 3:52 AM, Denys Dmytriyenko wrote:
> >BTW, can this be done in a separate recipe to add additional app clients,
> >instead of a patch to Weston? This is not scalable/portable at all...
> I take your point.
> For now, lets have this patch in this way. There have been no
> changes to the application for sometime.
> If it undergoes additional changes we will explore ways of combining
> them. There is an ongoing effort to consolidate applications so we
> will include this one as well.
A bit confused by your statement above...
I was talking about "SoC performance monitoring utilities" added by this patch
being Weston clients. In other words, they are just apps talking to Weston and
hence should be in own separate code bases built by separate recipes. Not as a
patch on top of Weston...
Are you saying if you don't envision any changes to these SoC monitoring apps,
then you'll keep on carrying them as a Weston patch?
--
Denys
next prev parent reply other threads:[~2017-03-15 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 18:31 [master] weston: Add SoC performance monitoring utilities Karthik Ramanan
2017-03-14 21:52 ` Denys Dmytriyenko
2017-03-14 22:22 ` Denys Dmytriyenko
2017-03-15 2:40 ` Karthik Ramanan
2017-03-15 15:26 ` Denys Dmytriyenko [this message]
2017-03-16 6:15 ` Karthik Ramanan
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=20170315152610.GT578@edge \
--to=denys@ti.com \
--cc=a0393906@ti.com \
--cc=meta-arago@arago-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.