From: Martin Jansa <martin.jansa@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/8] lttng-modules: re-enable ARM builds
Date: Fri, 25 Jul 2014 00:02:10 +0200 [thread overview]
Message-ID: <20140724220210.GO2492@jama> (raw)
In-Reply-To: <67ae6f8074e50a768143cac6a40fd8d16e2f5965.1406234258.git.bruce.ashfield@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
On Thu, Jul 24, 2014 at 04:41:52PM -0400, Bruce Ashfield wrote:
> With lttng 2.4.2 and gcc 4.9, we can now enable lttng-modules for ARM.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb b/meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
> index 5a99a5adae8b..d87374163556 100644
> --- a/meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
> +++ b/meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
> @@ -12,8 +12,7 @@ inherit module
>
> SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
>
> -# lttng currently blacklists arm with gcc-4.8
> -COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
> +COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips|arm).*-linux'
Please squash this to 2/8 otherwise there is no arm version between 2/8
and 6/8.
> SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
> file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
> --
> 1.8.1.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-07-24 22:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 20:41 [PATCH 0/8] kernel: linux-yocto 3.14, linux-yocto-dev 3.16 and dependencies Bruce Ashfield
2014-07-24 20:41 ` [PATCH 1/8] linux-yocto/3.14: vexpress and MVM firmware support Bruce Ashfield
2014-07-24 20:41 ` [PATCH 2/8] lttng-modules: update to 2.5.0 Bruce Ashfield
2014-07-25 13:21 ` Martin Jansa
2014-07-25 13:23 ` Bruce Ashfield
2014-07-25 13:36 ` Bruce Ashfield
2014-07-25 13:46 ` Martin Jansa
2014-07-25 13:48 ` Bruce Ashfield
2014-07-25 14:41 ` Richard Purdie
2014-08-12 11:33 ` Martin Jansa
2014-08-12 11:50 ` Laurentiu Palcu
2014-07-24 20:41 ` [PATCH 3/8] linux-yocto: x86_64: expand kernel stack to 16K Bruce Ashfield
2014-07-24 20:41 ` [PATCH 4/8] linux-yocto-dev: bump to v3.16+ Bruce Ashfield
2014-07-25 3:35 ` Saul Wold
2014-07-25 3:36 ` Bruce Ashfield
2014-07-25 3:44 ` Bruce Ashfield
2014-07-24 20:41 ` [PATCH 5/8] kernel: don't copy .so.dbg files into kernel source install Bruce Ashfield
2014-07-24 20:41 ` [PATCH 6/8] lttng-modules: re-enable ARM builds Bruce Ashfield
2014-07-24 22:02 ` Martin Jansa [this message]
2014-07-25 3:10 ` Bruce Ashfield
2014-07-25 9:53 ` Martin Jansa
2014-07-25 13:00 ` Bruce Ashfield
2014-07-25 13:14 ` Bruce Ashfield
2014-07-24 20:41 ` [PATCH 7/8] linux-yocto/3.14: libata and generic CPU modalias handling Bruce Ashfield
2014-07-24 20:41 ` [PATCH 8/8] kern-tools: adjust to full history meta-data Bruce Ashfield
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=20140724220210.GO2492@jama \
--to=martin.jansa@gmail.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@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