mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <borislav.petkov@amd.com>
Subject: [PATCH 0/2] tools: Add a toplevel Makefile
Date: Thu, 22 Mar 2012 18:01:51 +0100	[thread overview]
Message-ID: <1332435713-32143-1-git-send-email-bp@amd64.org> (raw)

From: Borislav Petkov <borislav.petkov@amd.com>

Hi all,

this is a refresh and carve-out of an old patchset. It adds a toplevel
Makefile to tools/ so that one can build the tool of her/his liking by
simply doing

$ cd tools/
$ make <toolname>

By default, we build perf. There's also a scripts/Makefile.lib now which
should contain all make-related generic stuff which can be used by all
tools' build process after including this file.

Any comments/suggestions are welcome,
thanks.

             reply	other threads:[~2012-03-22 17:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 17:01 Borislav Petkov [this message]
2012-03-22 17:01 ` [PATCH 1/2] tools: Add Makefile.lib Borislav Petkov
2012-03-22 21:07   ` Sam Ravnborg
2012-03-22 21:15     ` Borislav Petkov
2012-03-22 17:01 ` [PATCH 2/2] tools: Add a toplevel Makefile Borislav Petkov
2012-03-22 18:33   ` Christoph Lameter
2012-03-22 21:04     ` Borislav Petkov
2012-03-22 21:47       ` Christoph Lameter
2012-03-26 10:27         ` Pekka Enberg
2012-03-29 12:33           ` Borislav Petkov
2012-03-23 14:43 [PATCH 0/2] " Borislav Petkov
2012-03-24  7:44 ` Ingo Molnar
2012-03-26 12:26   ` 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

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=1332435713-32143-1-git-send-email-bp@amd64.org \
    --to=bp@amd64.org \
    --cc=acme@infradead.org \
    --cc=borislav.petkov@amd.com \
    --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

all inboxes | Powered by JetHome®