From: nitin.a.kamble@intel.com
To: richard.purdie@linuxfoundation.org, saul.wold@intel.com,
Openembedded-core@lists.openembedded.org,
bruce.ashfield@windriver.com, tom.zanussi@intel.com,
dvhart@linux.intel.com
Subject: [PATCH 0/1] A fix for the lttng-modules
Date: Thu, 25 Sep 2014 19:00:43 -0700 [thread overview]
Message-ID: <cover.1411695722.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
The lttng-modules recipe was failing with meta-intel BSPs with the
v3.17 kernel. The qemu machines from the poky layers did not get
hit by this issue. The accompanying commit fixes the issue observed in
the lttng-modules recipe. The fix is made in a way to not break on older
kernel versions.
This is tested with v3.10 and v3.17 kernels with meta-intel BSPs. I
understand that the oecore/poky layer has stopped taking commits for the
upcoming v1.7 release. Let me know, if this commit can not go in the
oecore/poky layer. In that case, this fix will instead be pushed to the
meta-intel layer.
Thanks,
Nitin
The following changes since commit 8ac8eca2e3bd8c78e2b31ea974930ed0243258a3:
build-appliance-image: Update to dizzy head revision (2014-09-23 22:10:26 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib nitin/misc
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
Nitin A Kamble (1):
lttng-modules: fix build issues with the v3.17 kernel
.../fix_build_with_v3.17_kernel.patch | 111 +++++++++++++++++++++
meta/recipes-kernel/lttng/lttng-modules_2.5.0.bb | 1 +
2 files changed, 112 insertions(+)
create mode 100644 meta/recipes-kernel/lttng/lttng-modules/fix_build_with_v3.17_kernel.patch
--
1.8.1.4
next reply other threads:[~2014-09-26 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 2:00 nitin.a.kamble [this message]
2014-09-26 2:00 ` [PATCH 1/1] lttng-modules: fix build issues with the v3.17 kernel nitin.a.kamble
2014-09-26 2:23 ` Bruce Ashfield
2014-09-26 16:23 ` Kamble, Nitin A
2014-09-26 17:20 ` Bruce Ashfield
2014-09-26 17:32 ` Kamble, Nitin A
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=cover.1411695722.git.nitin.a.kamble@intel.com \
--to=nitin.a.kamble@intel.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.com \
--cc=tom.zanussi@intel.com \
/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