All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lttng-modules: Update 2.7.3 -> 2.8.0+master
Date: Mon, 05 Sep 2016 15:44:11 +0100	[thread overview]
Message-ID: <1473086651.20226.14.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKq8Z8z4a7SoZoxzOz8GrEWnsoZZoL8Se++wMMWJp6yzsQ@mail.gmail.com>

On Mon, 2016-09-05 at 11:40 -0300, Otavio Salvador wrote:
> On Wed, Aug 31, 2016 at 7:32 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > We need master for the changes to work with 4.8 kernels.
> > 
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> This broken for kernels which does not enable CONFIG_TRACEPOINTS.
> 
> Up to now, the lttng-modules build were fine if this was disabled
> just
> printing a warning on the build. Now it makes build fail.
> 
> The behaviour changes was made on:
> 
> https://github.com/lttng/lttng-modules/commit/ca62d279e2e83fd46b8a04e
> 6ad4471e9f8fc7c47

Hmm, any idea how we should proceed then?

> Another thing I noticed is that we ought to be using stable-2.8
> branch or name the recipe accordingly as master is in fact 2.9-pre.

We'll need to rename it then as there are changes in master needed for
4.8 kernels which is why I upgraded it in the first place.

Cheers,

Richard


  reply	other threads:[~2016-09-05 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 10:32 [PATCH] lttng-modules: Update 2.7.3 -> 2.8.0+master Richard Purdie
2016-09-05 14:40 ` Otavio Salvador
2016-09-05 14:44   ` Richard Purdie [this message]
2016-09-05 14:45     ` Otavio Salvador

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=1473086651.20226.14.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.