Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/8] lttng-modules: update to 2.5.0
Date: Fri, 25 Jul 2014 15:21:58 +0200	[thread overview]
Message-ID: <20140725132158.GU2492@jama> (raw)
In-Reply-To: <48ca1900cd8400421948c4a2c33c722b979f3292.1406234258.git.bruce.ashfield@windriver.com>

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

On Thu, Jul 24, 2014 at 04:41:48PM -0400, Bruce Ashfield wrote:
> During the uprev of the yocto kernel to 3.16, lttng-modules failed to build.
> To grab the latest stable content, we update to 2.5.0, and add two patches
> to also make it build against 3.16+.
> 
> We also drop the older 2.3.3 lttng-modules, since it is no longer required
> to support ARM builds.
> 
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
>  ...compaction-instrumentation-to-3.16-kernel.patch | 83 ++++++++++++++++++++++
>  ...ate-vmscan-instrumentation-to-3.16-kernel.patch | 70 ++++++++++++++++++
>  meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb   | 36 ----------
>  ...tng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} |  7 +-
>  4 files changed, 157 insertions(+), 39 deletions(-)
>  create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-compaction-instrumentation-to-3.16-kernel.patch
>  create mode 100644 meta/recipes-kernel/lttng/lttng-modules/Update-vmscan-instrumentation-to-3.16-kernel.patch
>  delete mode 100644 meta/recipes-kernel/lttng/lttng-modules_2.3.3.bb
>  rename meta/recipes-kernel/lttng/{lttng-modules_2.4.1.bb => lttng-modules_2.5.0.bb} (85%)
> 

...

> diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb b/meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
> similarity index 85%
> rename from meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
> rename to meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
> index 5e05ffc69853..5a99a5adae8b 100644
> --- a/meta/recipes-kernel/lttng/lttng-modules_2.4.1.bb
> +++ b/meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb
> @@ -10,14 +10,15 @@ DEPENDS = "virtual/kernel"

Is the LICENSE = "LGPLv2.1 & GPLv2" correct?

git/LICENSE says:

* MIT-style license

These files are licensed under an MIT-style license. See mit-license.txt
for details.

lib/prio_heap/lttng_prio_heap.h
lib/prio_heap/lttng_prio_heap.c
lib/bitfield.h


>  
>  inherit module
>  
> -SRCREV = "a0383def517e3aebbbcebae61fe2bcfb50d31e71"
> -PV = "2.4.1"
> +SRCREV = "789fd1d06d07aeb9a403bdce1b3318560cfc6eca"
>  
>  # lttng currently blacklists arm with gcc-4.8
>  COMPATIBLE_HOST = '(x86_64|i.86|powerpc|aarch64|mips).*-linux'
>  
> -SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.4 \
> +SRC_URI = "git://git.lttng.org/lttng-modules.git;branch=stable-2.5 \
>             file://lttng-modules-replace-KERNELDIR-with-KERNEL_SRC.patch \
> +           file://Update-compaction-instrumentation-to-3.16-kernel.patch \
> +           file://Update-vmscan-instrumentation-to-3.16-kernel.patch \
>             "
>  
>  export INSTALL_MOD_DIR="kernel/lttng-modules"
> -- 
> 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 --]

  reply	other threads:[~2014-07-25 13:21 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 [this message]
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
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=20140725132158.GU2492@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