public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH 0/4] tools/perf/build: Improve 'make', 'make install' and 'make clean' output
Date: Wed,  9 Oct 2013 11:49:25 +0200	[thread overview]
Message-ID: <1381312169-17354-1-git-send-email-mingo@kernel.org> (raw)

This series improves perf's default 'make', 'make install' and 'make clean'
output messages: less console spam, more summaries, more consistency.

For example the new 'make install' output is now:

  comet:~/tip/tools/perf> make install
    BUILD:   Doing 'make -j12' parallel build
    SUBDIR   Documentation
    INSTALL  Documentation-man
    INSTALL  binaries
    INSTALL  libexec
    INSTALL  perf-archive
    INSTALL  perl-scripts
    INSTALL  python-scripts
    INSTALL  bash_completion-script
    INSTALL  tests

The Git tree can be found at:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tmp.perf

(The commits are top of the build system speedup patches.)

Thanks,

	Ingo

===============>
Ingo Molnar (4):
  tools/perf/build: Implement summary output for 'make clean'
  tools/build: Harmonize the various build messages in perf, lib-traceevent, lib-lk
  tools/perf/build: Align perf version output to other build messages
  tools/perf/build: Implement summary output for 'make install'

 tools/lib/traceevent/Makefile     | 18 +++++++--------
 tools/perf/Documentation/Makefile | 62 +++++++++++++++++++++++++++-----------------------
 tools/perf/Makefile               |  2 +-
 tools/perf/Makefile.perf          | 72 +++++++++++++++++++++++++++++++++--------------------------
 tools/perf/config/utilities.mak   |  8 +++++++
 tools/perf/util/PERF-VERSION-GEN  |  2 +-
 tools/scripts/Makefile.include    | 23 ++++++++++---------
 7 files changed, 105 insertions(+), 82 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2013-10-09  9:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  9:49 Ingo Molnar [this message]
2013-10-09  9:49 ` [PATCH 1/4] tools/perf/build: Implement summary output for 'make clean' Ingo Molnar
2013-10-15  5:31   ` [tip:perf/core] perf tools: Implement summary output for ' make clean' tip-bot for Ingo Molnar
2013-10-09  9:49 ` [PATCH 2/4] tools/build: Harmonize the various build messages in perf, lib-traceevent, lib-lk Ingo Molnar
2013-10-15  5:32   ` [tip:perf/core] tools: " tip-bot for Ingo Molnar
2013-10-09  9:49 ` [PATCH 3/4] tools/perf/build: Align perf version output to other build messages Ingo Molnar
2013-10-15  5:32   ` [tip:perf/core] perf tools: " tip-bot for Ingo Molnar
2013-10-09  9:49 ` [PATCH 4/4] tools/perf/build: Implement summary output for 'make install' Ingo Molnar
2013-10-15  5:32   ` [tip:perf/core] perf tools: Implement summary output for ' make install' tip-bot for Ingo Molnar

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=1381312169-17354-1-git-send-email-mingo@kernel.org \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.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