From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/8] lttng-modules: update to 2.5.0
Date: Fri, 25 Jul 2014 15:41:04 +0100 [thread overview]
Message-ID: <1406299264.27697.36.camel@ted> (raw)
In-Reply-To: <CADkTA4P0fQJjmQ_JwrodNSeYrhpjmTQbf=M9EXGOVMoDwoht1g@mail.gmail.com>
On Fri, 2014-07-25 at 09:48 -0400, Bruce Ashfield wrote:
> On Fri, Jul 25, 2014 at 9:46 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Fri, Jul 25, 2014 at 09:36:12AM -0400, Bruce Ashfield wrote:
> >> On Fri, Jul 25, 2014 at 9:23 AM, Bruce Ashfield
> >> <bruce.ashfield@gmail.com> wrote:
> >> > On Fri, Jul 25, 2014 at 9:21 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> >> 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?
> >> >
> >> > Let me double check. I was doing an update and test, and didn't notice if
> >> > this had changed.
> >> >
> >> > Even if it did change, and I'm just uprev'ing .. I'll fix it, since it
> >> > being wrong
> >> > in the past doesn't give me a free pass to keep it wrong in an update :)
> >>
> >> Too funny. There have been the three MIT licence files since 2011 .. so I agree
> >> that the recipe's summary is long. I'll tack a patch onto the end of the series
> >> and wait to hear from RP/Saul about anything else I may have broken.
> >
> > Sorry I thought you're maintainer of lttng-*, it seems like Laurentiu is
>
> No worries. I just get caught in the blast when lttng blows up during
> kernel uprevs, and I fix the wreckage so I can send out my updates :)
>
> If we don't hear from Laurentiu, I can still do the update, so I'll hold it
> as a separate patch here.
I'm having fun with email, this thread got split into several different
folders. I've merged the series after seeing the nightly builds pass ok
(nice work Bruce!) so I'll take any follow up patches to fix anything
like the LICENSE fields.
Cheers,
Richard
next prev parent reply other threads:[~2014-07-25 14:42 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 [this message]
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=1406299264.27697.36.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.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