From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] lttng-modules: Fix build with older kernels
Date: Tue, 20 May 2014 17:25:10 +0200 [thread overview]
Message-ID: <20140520152510.GB2424@jama> (raw)
In-Reply-To: <1400593365.28353.215.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Tue, May 20, 2014 at 02:42:45PM +0100, Richard Purdie wrote:
> On Thu, 2014-05-15 at 14:09 +0200, Martin Jansa wrote:
> > * forward port this patch from daisy:
> > commit c11b29ff4f24af0445c3c6a694b8dc2037dcd7e4
> > Author: Tom Zanussi <tom.zanussi@intel.com>
> > Date: Thu Mar 6 22:26:20 2014 -0600
> >
> > lttng-modules: Fix 3.14 bio tracepoints
> >
> > * how is it possible that it's in daisy but not in master?
>
> It looks like we have two versions of lttng-modules and friends. The
> patch was applied in master and daisy to 2.4.0 but not to 2.3.3.
>
> Why do we have two versions of the lttng pieces? :( One works on arm and
> the other doesn't?
>
> Anyhow, the change was in master and daisy.
Yes, in the end I've discovered it as well and sent separate patch for
daisy to apply the same patch in 2nd lttng-modules version:
http://lists.openembedded.org/pipermail/openembedded-core/2014-May/092593.html
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-05-20 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 12:09 [PATCH] lttng-modules: Fix build with older kernels Martin Jansa
2014-05-20 13:42 ` Richard Purdie
2014-05-20 14:01 ` Tom Zanussi
2014-05-20 15:25 ` Martin Jansa [this message]
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=20140520152510.GB2424@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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