From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] lttng-2.0: fix compiliation error
Date: Tue, 20 Mar 2012 15:49:19 -0700 [thread overview]
Message-ID: <4F69096F.8050604@intel.com> (raw)
In-Reply-To: <cover.1332179433.git.bruce.ashfield@windriver.com>
On 03/19/2012 10:53 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here's a fix for the recent lttng-2.0 modules build error that
> was reported. The recent -stable update created a collision with
> is_compat_task() that was already being defined as a fallback
> within lttng 2.0.
>
> I've made a patch fix, versus updating lttng-2.0 .. since churning
> this package would be a good idea right now.
>
> Cheers,
>
> Bruce
>
> The following changes since commit a9873f12e5ba11e1307440901d07e9642e9f53bf:
>
> pigz: Ensure DEPENDS on zlib exists for native and target versions (2012-03-19 14:37:46 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
> compliation error with 3.2.x -stable kernels
>
> ...ls-protect-is_compat_task-from-redefiniti.patch | 41 ++++++++++++++++++++
> .../lttng-2.0/lttng-modules_2.0.pre11.bb | 3 +-
> 2 files changed, 43 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-kernel/lttng-2.0/lttng-modules/lttng-sycalls-protect-is_compat_task-from-redefiniti.patch
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-03-20 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 17:53 [PATCH 0/1] lttng-2.0: fix compiliation error Bruce Ashfield
2012-03-19 17:53 ` [PATCH 1/1] lttng-modules: fix compliation error with 3.2.x -stable kernels Bruce Ashfield
2012-03-20 22:49 ` Saul Wold [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=4F69096F.8050604@intel.com \
--to=saul.wold@intel.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