Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/2] Breakpad and ktap recipes
Date: Fri, 18 Oct 2013 11:40:09 +0200	[thread overview]
Message-ID: <20131018094009.GF3930@jama> (raw)
In-Reply-To: <cace5960-a68e-4774-911d-debd3fc71b6d@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]

On Fri, Oct 18, 2013 at 07:14:09AM +0200, Anders Darander wrote:
> I'm going to resend this series with the correct prefix added. 

Are they the same, just with prefix added?

I've already included them in last jenkins builds, so to know if I
should fetch new version from patchwork or not.

> Anders Darander <anders@chargestorm.se> wrote:
> >
> >These are a couple of recipes that we've been using internally for some
> >time. They
> >were developed and mostly used on a dylan-based setup. Testing has
> >primarily been 
> >performed on ARM, both qemuarm and our custom machine.
> >
> >Breakpad is a crash reporting tool, that's getting a wider use.
> >Please, let me know if there's a more efficient way (or otherwise
> >better way) to 
> >have the bbclass generate the symbol file.
> >
> >Ktap is a new scripting dynamic tracing tool for Linux. This recipe
> >will be of
> >use until everyone is on 3.13+ kernels (ktap has been merged for the
> >3.13 series).
> >
> >The following changes since commit
> >f8903f53db717294d63a8d79b5ef7ca34b3c189e:
> >
> >libhugetlbfs: install perl lib to directory perl instead of perl5
> >(2013-10-15 13:43:53 +0200)
> >
> >are available in the git repository at:
> >
> >  git://github.com/darander/meta-oe breakpad-ktap
> >  https://github.com/darander/meta-oe/tree/breakpad-ktap
> >
> >Anders Darander (2):
> >  breakpad: add initial recipe
> >  ktap: add initial recipe
> >
> > meta-oe/classes/breakpad.bbclass                  | 32 ++++++++++
> >meta-oe/recipes-devtools/breakpad/breakpad_svn.bb | 72
> >+++++++++++++++++++++++
> > meta-oe/recipes-kernel/ktap/ktap-module_0.3.bb    | 19 ++++++
> > meta-oe/recipes-kernel/ktap/ktap.inc              | 11 ++++
> > meta-oe/recipes-kernel/ktap/ktap_0.3.bb           | 17 ++++++
> > 5 files changed, 151 insertions(+)
> > create mode 100644 meta-oe/classes/breakpad.bbclass
> > create mode 100644 meta-oe/recipes-devtools/breakpad/breakpad_svn.bb
> > create mode 100644 meta-oe/recipes-kernel/ktap/ktap-module_0.3.bb
> > create mode 100644 meta-oe/recipes-kernel/ktap/ktap.inc
> > create mode 100644 meta-oe/recipes-kernel/ktap/ktap_0.3.bb
> 
> -- 
> ChargeStorm AB / eStorm 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-10-18  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 10:45 [PATCH 0/2] Breakpad and ktap recipes Anders Darander
2013-10-16 10:45 ` [PATCH 1/2] breakpad: add initial recipe Anders Darander
2013-10-16 10:45 ` [PATCH 2/2] ktap: " Anders Darander
2013-10-18  5:14 ` [PATCH 0/2] Breakpad and ktap recipes Anders Darander
2013-10-18  9:40   ` Martin Jansa [this message]
2013-10-19  8:17     ` Anders Darander
2013-10-19 14:10       ` Martin Jansa

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=20131018094009.GF3930@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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