All of lore.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>
Subject: Re: [PATCH 0/2] tools: Add a toplevel Makefile
Date: Mon, 26 Mar 2012 17:14:32 +0200	[thread overview]
Message-ID: <20120326151432.GA8527@gmail.com> (raw)
In-Reply-To: <20120326122632.GC32090@aftab>


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

> On Sat, Mar 24, 2012 at 08:44:12AM +0100, Ingo Molnar wrote:
> > 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
> 
> Well,
> 
> you could do
> 
> $ make -j -C tools perf

Arguably I could also type:

  cd tools/perf; make -j install

:-)

So I just wanted to bring this up, that integrating it into the 
top level Makefile might make sense. Or not.

Thanks,

	Ingo

  parent reply	other threads:[~2012-03-26 15:14 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 ` [PATCH 0/2] tools: Add a toplevel Makefile Ingo Molnar
2012-03-26 12:26   ` Borislav Petkov
2012-03-26 14:05     ` Borislav Petkov
2012-03-26 15:14     ` Ingo Molnar [this message]
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=20120326151432.GA8527@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@infradead.org \
    --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 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.