From: otavio@ossystems.com.br (Otavio Salvador)
Subject: [lttng-dev] lttng-modules build failure for 3.12-rc6
Date: Mon, 4 Nov 2013 15:37:41 -0200 [thread overview]
Message-ID: <CAP9ODKqx6ZENmxa7R-h9o7avR7jm5JhM_oX7M4BwtmpBx1J=Lg@mail.gmail.com> (raw)
In-Reply-To: <468459233.56635.1383586483940.JavaMail.zimbra@efficios.com>
On Mon, Nov 4, 2013 at 3:34 PM, Mathieu Desnoyers
<mathieu.desnoyers at efficios.com> wrote:
> ----- Original Message -----
>> From: "Otavio Salvador" <otavio@ossystems.com.br>
>> To: "Mathieu Desnoyers" <mathieu.desnoyers at efficios.com>
>> Cc: "lttng-dev" <lttng-dev at lists.lttng.org>
>> Sent: Thursday, October 31, 2013 2:21:21 PM
>> Subject: Re: lttng-modules build failure for 3.12-rc6
>>
>> On Thu, Oct 31, 2013 at 4:05 PM, Mathieu Desnoyers
>> <mathieu.desnoyers at efficios.com> wrote:
>> ...
>> >> >> Great; can you backport those to stable-2.3? I'd like to send the
>> >> >> update for Yocto including these changes and fix it for us directly
>> >> >> there.
>> >> >
>> >> > Strictly speaking, supporting a new kernel can be seen as a new feature.
>> >> > stable-2.3 was released for 3.11. Moreover, 3.12 kernel is still in rc
>> >> > stage, so things can still change (and even be reverted, this has
>> >> > happened
>> >> > in the past).
>> >> >
>> >> > Unfortunately, we don't add features in the stable branches, only bug
>> >> > fixes. But keep in mind that 2.4 should come within the coming weeks.
>> >>
>> >> Humm in this case stable-2.3 should had a #warning saying it support
>> >> kernels up to 3.11 only. As it does not state it somewhere it seems
>> >> like a fix for me.
>> >>
>> >> I will end doing the backport in this case, but it is something which
>> >> could be fixed for 2.4 than and include such warning.
>> >
>> > I just discussed this with David and Julien, and here is what we came up
>> > with:
>> >
>> > - when a final kernel release comes up (e.g. 3.12), it makes sense to add
>> > support for it into a stable release if the modifications are small,
>> > - however, it does not make sense to add support for a release candidate
>> > Linux kernel, since those are known to change a lot during the RC cycle,
>> > (chasing a moving target is never fun)
>> >
>> > Therefore, I'd be open to cherry-pick the master commits into stable-2.3
>> > when 3.12 final comes out. I don't promise I'll remember to do so, so a
>> > gentle "ping" when 3.12 final comes out to remind me which commit ID I
>> > should cherry-pick from master into stable-2.3 would be welcome,
>>
>> Right; it is fine with me. We're close to it as we're in 3.12-rc7.
>
> FYI, I just pushed 3.12 linux kernel support in lttng-modules master and stable-2.3 branches. Please let me know if you see any issue.
Great; thanks.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
prev parent reply other threads:[~2013-11-04 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP9ODKoqhtXmS94ZtV8hNPs=kUXWLU9msN+GR7Zf9DQrdQUmSg@mail.gmail.com>
[not found] ` <1567008261.54443.1383229577346.JavaMail.zimbra@efficios.com>
[not found] ` <CAP9ODKrLtSuFJUKryO9RJ5BHri9d7gL+5vZqOAw-o_OZ7cZn6A@mail.gmail.com>
[not found] ` <544819642.54467.1383230288963.JavaMail.zimbra@efficios.com>
[not found] ` <CAP9ODKokvCH16Qwq6ftBvWLpRHo+=T_1SggJa-3GOcy7aE2yeA@mail.gmail.com>
[not found] ` <1328648078.54590.1383242720354.JavaMail.zimbra@efficios.com>
[not found] ` <CAP9ODKrdOhk9o=3yxo0189Xtzgpx=Fo5MLDTq9C7Zt9Y8e2a2Q@mail.gmail.com>
2013-11-04 17:34 ` Mathieu Desnoyers
2013-11-04 17:37 ` Otavio Salvador [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='CAP9ODKqx6ZENmxa7R-h9o7avR7jm5JhM_oX7M4BwtmpBx1J=Lg@mail.gmail.com' \
--to=otavio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox