openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>,
	zhe he <zhe.he@windriver.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] lttng: babeltrace: Fix negative clock offset
Date: Tue, 03 Sep 2019 21:56:48 +0100	[thread overview]
Message-ID: <8a31bcb75bee9ee5bd1c4e44c9757d8cf7986308.camel@linuxfoundation.org> (raw)
In-Reply-To: <1774382209.769.1567544016190.JavaMail.zimbra@efficios.com>

On Tue, 2019-09-03 at 16:53 -0400, Jonathan Rajotte-Julien wrote:
> Hi,
> 
> This patch breaks the API of stable-1.5. It is clearly mentioned in
> the commit message:
> 
>  It introduces API-breaking changes in the C and Python APIs, since
> we
>  need to be able to return negative time values, which were
> previously
>  used as errors (-1ULL).
> 
> You can have it in your layer but it should never be upstreamed to
> yocto/oe in any case for the stable 1.5 branch of babeltrace.
> 
> The change you are referencing
> (61cf588beae752e5ddfc60b6b5310f769ac9e852) is queued to be in
> Babeltrace 2.0.0.
> 
> Richard: as part of the lttng/babeltrace team I advice against using
> this patch in OE.

Thanks, it was in master-next but its now been removed locally and will
propagate. I appreciate the advice.

Cheers,

Richard



      reply	other threads:[~2019-09-03 20:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  3:09 [PATCH] lttng: babeltrace: Fix negative clock offset zhe.he
2019-09-03 20:53 ` Jonathan Rajotte-Julien
2019-09-03 20:56   ` richard.purdie [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=8a31bcb75bee9ee5bd1c4e44c9757d8cf7986308.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jonathan.rajotte-julien@efficios.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=zhe.he@windriver.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;
as well as URLs for NNTP newsgroup(s).