public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@amd64.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH 0/2] tools: Add a toplevel Makefile
Date: Sat, 24 Mar 2012 08:44:12 +0100	[thread overview]
Message-ID: <20120324074412.GE20145@gmail.com> (raw)
In-Reply-To: <1332513788-9726-1-git-send-email-bp@amd64.org>


* Borislav Petkov <bp@amd64.org> wrote:

> From: Borislav Petkov <borislav.petkov@amd.com>
> 
> Hi all,
> 
> here's a refreshed version from yesterday incorporating all comments and
> suggestions along with a third patch that adds a 'help' target as the
> default one causing the following below. Btw, Arnaldo, could you please
> pick those up if there are no complaints since the first patch touches
> perf and I don't have a clear idea who else to send it to anyway :).
> 
> Thanks.
> 
> $ make

Could this also be accessible via 'make tools' in the toplevel 
Makefile?

I'd love to be able to type:

  make -j tools perf install

But ... your current patches are an improvement as well, this 
list alone:

> $ make
> Possible targets:
> 
>   cpupower   - a tool for all things x86 CPU power
>   firewire   - the userspace part of nosy, an IEEE-1394 traffic sniffer
>   lguest     - a minimal 32-bit x86 hypervisor
>   perf       - Linux performance measurements tool
>   slub       - slabs reporting tool
>   turbostat  - Intel CPU idle stats and freq reporting tool
>   usb        - USB testing tools
>   virtio     - vhost test module
>   x86_energy_perf_policy - Intel energy policy tool

is already pretty useful.

Btw., please fix the perf line to say:

s/performance measurements tool/performance measurement and analysis tool

Thanks,

	Ingo

  parent reply	other threads:[~2012-03-24  7:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 14:43 [PATCH 0/2] tools: Add a toplevel Makefile Borislav Petkov
2012-03-23 14:43 ` [PATCH 1/3] tools: Add Makefile.include Borislav Petkov
2012-03-23 14:43 ` [PATCH 2/3] tools: Add a toplevel Makefile Borislav Petkov
2012-03-23 14:43 ` [PATCH 3/3] tools: Add a help target Borislav Petkov
2012-03-24  7:44 ` Ingo Molnar [this message]
2012-03-26 12:26   ` [PATCH 0/2] tools: Add a toplevel Makefile Borislav Petkov
2012-03-26 14:05     ` Borislav Petkov
2012-03-26 15:14     ` Ingo Molnar
2012-03-26 15:41       ` Borislav Petkov
2012-03-28  7:25         ` Ingo Molnar
2012-03-28  9:51           ` Borislav Petkov
2012-03-28 17:57             ` Borislav Petkov
2012-03-29 11:21               ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2012-03-22 17:01 Borislav Petkov

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=20120324074412.GE20145@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@infradead.org \
    --cc=borislav.petkov@amd.com \
    --cc=bp@amd64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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