From: Adrian Bunk <bunk@stusta.de>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>,
Jeremie Galarneau <jgalar@efficios.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] lttng-modules: Backport patches to fix compilation failures since kernel v5.1
Date: Wed, 12 Jun 2019 16:27:41 +0300 [thread overview]
Message-ID: <20190612132741.GB23143@localhost> (raw)
In-Reply-To: <1859381600.42862.1560337102909.JavaMail.zimbra@efficios.com>
On Wed, Jun 12, 2019 at 06:58:22AM -0400, Mathieu Desnoyers wrote:
>...
> We always integrate support for newer kernel versions instrumentation back
> into our current stable release. So as soon as 5.2 final comes out, we will
> release a 2.10.x version including support for it in lttng-modules.
>...
Did something go wrong with that for 5.1?
This discussion started with patches on top of 2.10.9 for 5.1 support.
If the missing release was just a one-time problem for 5.1,
then the whole problem is usually confined to -rc kernels.
> Thanks,
>
> Mathieu
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-06-12 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 9:03 [PATCH v2] lttng-modules: Backport patches to fix compilation failures since kernel v5.1 zhe.he
2019-06-11 22:49 ` Richard Purdie
2019-06-11 22:57 ` Bruce Ashfield
2019-06-25 7:59 ` He Zhe
2019-06-25 8:04 ` richard.purdie
2019-06-25 9:49 ` He Zhe
2019-06-12 9:14 ` He Zhe
2019-06-12 10:51 ` Adrian Bunk
2019-06-12 10:58 ` Mathieu Desnoyers
2019-06-12 11:10 ` He Zhe
2019-06-12 11:29 ` Mathieu Desnoyers
2019-06-12 12:32 ` He Zhe
2019-06-12 14:52 ` Jonathan Rajotte-Julien
2019-06-12 14:56 ` Jonathan Rajotte-Julien
2019-06-14 2:33 ` He Zhe
2019-06-12 13:27 ` Adrian Bunk [this message]
2019-06-12 13:33 ` Mathieu Desnoyers
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=20190612132741.GB23143@localhost \
--to=bunk@stusta.de \
--cc=jgalar@efficios.com \
--cc=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.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