From: Darren Hart <dvhart@linux.intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/3] tracing: trace-cmd fixes and new kernelshark recipe
Date: Thu, 30 Dec 2010 09:57:04 -0800 [thread overview]
Message-ID: <cover.1293731824.git.dvhart@linux.intel.com> (raw)
This series fixes some issues with the existing trace-cmd recipe and adds
a new recipe for kernelshark. The latter catches a bug in glib-2.0 which
is also addressed in this series with a patch from Open Embedded.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: dvhart/tracing
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/tracing
Thanks,
Darren Hart <dvhart@linux.intel.com>
---
Darren Hart (3):
trace-cmd: fix cross-compilation
glib-2.0: fix g_once_init_enter compile failure
kernelshark: add ftrace gui viewer
.../glib-2.0-2.27.3/g_once_init_enter.patch | 13 ++++++++++++
meta/recipes-core/glib-2.0/glib-2.0_2.27.3.bb | 6 +++-
meta/recipes-kernel/trace-cmd/kernelshark_git.bb | 21 ++++++++++++++++++++
meta/recipes-kernel/trace-cmd/trace-cmd_git.bb | 12 ++++------
4 files changed, 43 insertions(+), 9 deletions(-)
create mode 100644 meta/recipes-core/glib-2.0/glib-2.0-2.27.3/g_once_init_enter.patch
create mode 100644 meta/recipes-kernel/trace-cmd/kernelshark_git.bb
next reply other threads:[~2010-12-30 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 17:57 Darren Hart [this message]
2010-12-29 1:10 ` [PATCH 3/3] kernelshark: add ftrace gui viewer Darren Hart
2010-12-31 8:01 ` Saul Wold
2010-12-31 18:39 ` Darren Hart
2010-12-29 1:17 ` [PATCH 1/3] trace-cmd: fix cross-compilation Darren Hart
2010-12-30 21:02 ` Bruce Ashfield
2010-12-30 22:29 ` Darren Hart
2010-12-31 6:08 ` Bruce Ashfield
2010-12-31 7:41 ` Darren Hart
2010-12-31 13:12 ` Bruce Ashfield
2010-12-29 18:10 ` [PATCH 2/3] glib-2.0: fix g_once_init_enter compile failure Darren Hart
2010-12-31 8:05 ` Saul Wold
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=cover.1293731824.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=poky@yoctoproject.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.