From: Markus Mayer <code@mmayer.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] Add linux-tool-tmon
Date: Tue, 4 Jul 2017 16:54:43 -0700 [thread overview]
Message-ID: <20170704235445.35255-1-code@mmayer.net> (raw)
From: Markus Mayer <mmayer@broadcom.com>
Linux includes a tool for thermal monitoring (linux/tools/thermal/tmon).
This series enables building this tool alongside other userspace tools
bundled with the Linux kernel (known in buildroot as linux-tools).
In order to add linux-tool-tmon, we need to first stop relying on
alphabetical sorting of the linux-tool*.mk files.
Currently, the build system relies on linux-tool-*.mk files (i.e. the
sub-makefiles) to be sorted alphabetically such that linux-tools.mk
(the main makefile for linux-tools) will come last, therefore ensuring
that the sub-makefiles are included before the main makefile. So far,
this assumption has held true. Unfortunately, linux-tool-tmon.mk breaks
it. Sorted in the C locale, linux-tool-tmon.mk comes after
linux-tools.mk.
To ensure that the inclusion order remains correct, the logic to
include the linux-tool*mk has been modified.
Markus Mayer (2):
Makefile: don't rely on linux-tools being sorted alphabetically
package/linux-tools: add tmon
Makefile | 6 +++++-
package/linux-tools/Config.in | 7 +++++++
package/linux-tools/linux-tool-tmon.mk | 30 ++++++++++++++++++++++++++++++
package/linux-tools/linux-tools.mk | 8 +++-----
4 files changed, 45 insertions(+), 6 deletions(-)
create mode 100644 package/linux-tools/linux-tool-tmon.mk
--
2.13.0
next reply other threads:[~2017-07-04 23:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 23:54 Markus Mayer [this message]
2017-07-04 23:54 ` [Buildroot] [PATCH 1/2] Makefile: don't rely on linux-tools being sorted alphabetically Markus Mayer
2017-07-05 7:25 ` Yann E. MORIN
2017-07-05 7:38 ` Yann E. MORIN
2017-07-05 8:15 ` Arnout Vandecappelle
2017-07-05 8:09 ` Arnout Vandecappelle
2017-07-05 8:18 ` Arnout Vandecappelle
[not found] ` <CAGt4E5ueb6x_S4ff=dAeK-x9JnO1SmhnUGz+Q3XKUtj6s24L_Q@mail.gmail.com>
2017-07-05 17:19 ` Markus Mayer
2017-07-08 21:16 ` Arnout Vandecappelle
2017-07-09 0:00 ` Markus Mayer
2017-07-09 8:13 ` Yann E. MORIN
2017-07-09 11:10 ` Arnout Vandecappelle
2017-07-09 12:41 ` Yann E. MORIN
2017-07-10 3:49 ` Markus Mayer
2017-07-13 20:16 ` Markus Mayer
2017-07-13 21:45 ` Yann E. MORIN
2017-07-13 23:59 ` Markus Mayer
2017-07-16 15:08 ` Yann E. MORIN
2017-07-17 7:37 ` Thomas Petazzoni
2017-07-17 15:36 ` Yann E. MORIN
2017-07-17 17:32 ` Markus Mayer
2017-07-04 23:54 ` [Buildroot] [PATCH 2/2] package/linux-tools: add tmon Markus Mayer
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=20170704235445.35255-1-code@mmayer.net \
--to=code@mmayer.net \
--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 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.