From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] oprofile: Include operf command
Date: Fri, 27 Jan 2017 21:55:20 +1300 [thread overview]
Message-ID: <20170127215520.771ca1c4@free-electrons.com> (raw)
In-Reply-To: <1482453206.8507.24.camel@kymetacorp.com>
Hello,
On Fri, 23 Dec 2016 00:32:40 +0000, Trent Piepho wrote:
> This is the main command to control oprofile. It was introduced in
> version 0.9.8 from 2012-08-27 and in version 1.0.0 the previous
> control tool, opcontrol, was removed.
>
> In commit 9863553fe8fa16a4d19f652b409a44bb58ef5567, removing avr32
> support, code that added operf for !avr32 was removed rather than
> keeping the code but making it non-conditional.
>
> Signed-off-by: Trent Piepho <tpiepho@kymetacorp.com>
> ---
> package/oprofile/oprofile.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-01-27 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 0:32 [Buildroot] [PATCH] oprofile: Include operf command Trent Piepho
2017-01-27 8:55 ` Thomas Petazzoni [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=20170127215520.771ca1c4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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