From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/5] lttng-modules: bump to version 2.8.3
Date: Sun, 30 Oct 2016 23:18:45 +0100 [thread overview]
Message-ID: <20161030221845.GB12907@free.fr> (raw)
In-Reply-To: <CAB4xu_3U3qskp+x4mqFqRRmMmLb6XDuiH5toQujR=AwevgQZQQ@mail.gmail.com>
Philippe, All,
On 2016-10-30 18:13 -0400, Philippe Proulx spake thusly:
> On Sun, Oct 30, 2016 at 5:41 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2016-10-30 15:56 -0400, Philippe Proulx spake thusly:
> >> LTTng-modules has its own Makefile to build its modules. In particular,
> >> starting from v2.8, LTTng-modules has a way to be included as part of a
> >> Linux kernel image, that is, not as loadable kernel modules. This
> >> implies that additional environment variables need to be passed to the
> >> Makefile and kernel build system.
[--SNIP--]
> > I stand by the fact that we should use the kernel-modules infra, if it
> > can be made to work with specifying just the few new variables that are
> > needed, as explained above.
> >
> > If not possible, then provide an explanation why this is not sufficient.
>
> It's definitely possible. I changed it because upstream said that it's better to
> use their own Makefile as they can add new variables without having to
> track them in the distribution build systems. I can convert it back to using the
> the kernel-module infra if you prefer. I have no other arguments.
Well, what is different from a package that adds, removes or renames a
configure option? We downstreams have to deal with those changes every
bump we do anyway.
All we need is that upstreams provide such information in the the docs.
So, I still prefer we keep using the kernel-module infra.
Thanks for the feedback! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-10-30 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 19:56 [Buildroot] [PATCH v2 0/5] Update LTTng packages to 2.8.x and Babeltrace to 1.4.0 Philippe Proulx
2016-10-30 19:56 ` [Buildroot] [PATCH v2 1/5] lttng-libust: bump to version 2.8.1 Philippe Proulx
2016-10-30 20:56 ` Yann E. MORIN
2016-10-30 22:05 ` Philippe Proulx
2016-10-30 19:56 ` [Buildroot] [PATCH v2 2/5] lttng-tools: bump to version 2.8.2 Philippe Proulx
2016-10-30 21:12 ` Yann E. MORIN
2016-10-30 19:56 ` [Buildroot] [PATCH v2 3/5] lttng-tools: remove dependency on host-lttng-babeltrace Philippe Proulx
2016-10-30 21:24 ` Yann E. MORIN
2016-10-30 22:07 ` Philippe Proulx
2016-10-30 22:20 ` Yann E. MORIN
2016-10-30 19:56 ` [Buildroot] [PATCH v2 4/5] lttng-modules: bump to version 2.8.3 Philippe Proulx
2016-10-30 21:41 ` Yann E. MORIN
2016-10-30 22:13 ` Philippe Proulx
2016-10-30 22:18 ` Yann E. MORIN [this message]
2016-10-30 19:56 ` [Buildroot] [PATCH v2 5/5] lttng-babeltrace: bump to version 1.4.0 Philippe Proulx
2016-10-30 22:06 ` Yann E. MORIN
2016-10-30 22:31 ` Philippe Proulx
2016-10-30 20:36 ` [Buildroot] [PATCH v2 0/5] Update LTTng packages to 2.8.x and Babeltrace to 1.4.0 Yann E. MORIN
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=20161030221845.GB12907@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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