From: "Woegerer, Paul" <Paul_Woegerer@mentor.com>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Christopher Larson <chris_larson@mentor.com>,
openembedded-core@lists.openembedded.org
Subject: Re: lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2
Date: Tue, 15 Oct 2013 08:50:03 +0200 [thread overview]
Message-ID: <525CE59B.4050600@mentor.com> (raw)
In-Reply-To: <1381768366.19281.64.camel@empanada>
On 10/14/2013 06:32 PM, Tom Zanussi wrote:
> On Mon, 2013-10-14 at 17:54 +0200, Woegerer, Paul wrote:
>> lttng-modules 2.3.2 contains preprocessor-code that makes sure that
>> building of lttng-modules fails for the unlucky combinations of kernel
>> and lttng-modules. The problem is when we update our lttng-modules 2.3.0
>> to 2.3.2 then we would have lttng-modules failing to build for our qemu*
>> MACHINEs.
>>
>> Any recommendations on how we should address this ?
> Probably just get Bruce to update linux-yocto-3.10 to 3.10.14,
That would be the ideal solution.
--
Paul
>
> Tom
>
>> Many thanks,
>> Paul
>>
>
--
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division
prev parent reply other threads:[~2013-10-15 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 15:54 lttng-modules may trigger deadlock in the timekeeping subsystem with Linux <= 3.10.13, <= 3.11.2 Woegerer, Paul
2013-10-14 16:32 ` Tom Zanussi
2013-10-14 22:19 ` Tom Zanussi
2013-10-14 22:50 ` Bruce Ashfield
2013-10-15 6:59 ` Woegerer, Paul
2013-10-15 6:50 ` Woegerer, Paul [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=525CE59B.4050600@mentor.com \
--to=paul_woegerer@mentor.com \
--cc=chris_larson@mentor.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.zanussi@linux.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