From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2 v3] linux/tools: move to their own package (branch yem/linux-tools)
Date: Tue, 6 Sep 2016 16:29:11 +0200 [thread overview]
Message-ID: <cover.1473171931.git.yann.morin.1998@free.fr> (raw)
Hello All!
This series moves the Linux tools (cpupower, perf and selftests) our of
the linux package and into their own package.
As extensively explained in the commit log from the first patch, some
configurations are unbuildable, because they cause circular dependencies
in our Makefiles.
We fix that by moving the Linux tools to their own package.
Changes v2 -> v3:
- don't symlink the Linux sources; just build in there
- typoes
Changes v1 -> v2:
- properly handle legacy
Regards,
Yann E. MORIN.
The following changes since commit e03cb2eb2edf73b79156e8f54c80d04dc0846e89
libgtk3: fix typo (2016-09-05 23:36:04 +0200)
are available in the git repository at:
git://git.buildroot.org/~ymorin/git/buildroot.git
for you to fetch changes up to bdadcf3de3e5617f0492d88329476963a06fad44
docs/manual: update the linux tools section (2016-09-06 15:22:54 +0200)
----------------------------------------------------------------
Yann E. MORIN (2):
linux/tools: make it a real, separate package
docs/manual: update the linux tools section
Config.in.legacy | 24 +++++++++++
.../adding-packages-linux-kernel-spec-infra.txt | 40 +++++++++---------
linux/Config.in | 2 +-
linux/linux.mk | 24 +----------
.../linux-tools/Config.in | 14 +++++--
.../linux-tools}/linux-tool-cpupower.mk | 8 ++--
{linux => package/linux-tools}/linux-tool-perf.mk | 18 ++++----
.../linux-tools}/linux-tool-selftests.mk | 14 +++----
package/linux-tools/linux-tools.mk | 48 ++++++++++++++++++++++
9 files changed, 126 insertions(+), 66 deletions(-)
rename linux/Config.tools.in => package/linux-tools/Config.in (83%)
rename {linux => package/linux-tools}/linux-tool-cpupower.mk (79%)
rename {linux => package/linux-tools}/linux-tool-perf.mk (84%)
rename {linux => package/linux-tools}/linux-tool-selftests.mk (65%)
create mode 100644 package/linux-tools/linux-tools.mk
--
.-----------------.--------------------.------------------.--------------------.
| 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 reply other threads:[~2016-09-06 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 14:29 Yann E. MORIN [this message]
2016-09-06 14:29 ` [Buildroot] [PATCH 1/2 v3] linux/tools: make it a real, separate package Yann E. MORIN
2016-09-22 10:51 ` Thomas Petazzoni
2016-09-22 16:33 ` Yann E. MORIN
2016-09-22 14:58 ` Peter Korsgaard
2016-09-22 17:49 ` Thomas Petazzoni
2016-09-22 18:01 ` Peter Korsgaard
2016-09-22 18:14 ` Thomas Petazzoni
2016-09-22 18:17 ` Peter Korsgaard
2016-09-06 14:29 ` [Buildroot] [PATCH 2/2 v3] docs/manual: update the linux tools section Yann E. MORIN
2016-09-22 10:56 ` Thomas Petazzoni
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=cover.1473171931.git.yann.morin.1998@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