From: Borislav Petkov <bp@amd64.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Michal Marek <mmarek@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH v4 4/4] tools: Connect to the kernel build system
Date: Tue, 10 Apr 2012 23:04:57 +0200 [thread overview]
Message-ID: <20120410210457.GD30366@aftab> (raw)
In-Reply-To: <20120410203733.GD28293@merkur.ravnborg.org>
On Tue, Apr 10, 2012 at 10:37:33PM +0200, Sam Ravnborg wrote:
> On Tue, Apr 10, 2012 at 05:20:40PM +0200, Borislav Petkov wrote:
> > From: Borislav Petkov <borislav.petkov@amd.com>
> >
> > Now you can do
> >
> > $ make tools/<toolname>
> >
> > from the toplevel kernel directory and have the respective tool built.
> >
> > If you want to build and install it, do
> >
> > $ make tools/<toolname>_install
> >
> > $ make tools/<toolname>_clean
> >
> > should clean the respective tool directories.
> >
> > If you want to clean all in tools, simply do
> >
> > $ make tools/clean
> >
> > Also, if you want to get what the possible targets are, simply calling
> >
> > $ make tools/
> >
> > should give you the short help.
> >
> > $ make tools/install
> >
> > installs all tools, of course. Doh.
> >
> > Cc: Sam Ravnborg <sam@ravnborg.org>
> > Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
> > ---
> > Makefile | 7 +++++++
> > tools/Makefile | 25 ++++++++++++++++++++++++-
> > 2 files changed, 31 insertions(+), 1 deletion(-)
> >
> > diff --git a/Makefile b/Makefile
> > index 0df3d003a079..e24ce7104f63 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1468,6 +1468,13 @@ kernelrelease:
> > kernelversion:
> > @echo $(KERNELVERSION)
> >
> > +# Clear a bunch of variables before executing the submake
> > +tools/: FORCE
> > + $(Q)$(MAKE) LDFLAGS= -C $(src)/tools/
> I think you need to clear MAKEFLAGS here too?
>
> > +
> > +tools/%: FORCE
> > + $(Q)$(MAKE) LDFLAGS= MAKEFLAGS= -C $(src)/tools/ $*
> > +
>
> >
> > -perf firewire lguest usb virtio vm: FORCE
> > +firewire lguest perf usb virtio vm: FORCE
> > $(QUIET_SUBDIR0)$@/ $(QUIET_SUBDIR1)
>
> Fold this into 2/4
>
> >
> > cpupower: FORCE
> > @@ -32,6 +42,19 @@ turbostat x86_energy_perf_policy: FORCE
> > selftests: FORCE
> > $(QUIET_SUBDIR0)testing/$@/ $(QUIET_SUBDIR1)
> >
> > +firewire_install lguest_install perf_install usb_install virtio_install vm_install:
> > + $(QUIET_SUBDIR0)$(@:_install=)/ $(QUIET_SUBDIR1) install
> > +
> > +cpupower_install:
> > + $(QUIET_SUBDIR0)power/$(@:_install=)/ $(QUIET_SUBDIR1) install
> > +
> > +turbostat_install x86_energy_perf_policy_install:
> > + $(QUIET_SUBDIR0)power/x86/$(@:_install=)/ $(QUIET_SUBDIR1) install
> > +
> > +install: firewire_install lguest_install perf_install usb_install \
> > + virtio_install vm_install cpupower_install turbostat_install \
> > + x86_energy_perf_policy_install
> > +
>
> This really belongs in 2/4 or a separate patch.
>
> Sorry for bing picky about these details - but they destroy
> an otherwise fine patch-set.
Agreed with all above, will rework soon.
Thanks for looking at those.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
prev parent reply other threads:[~2012-04-10 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 15:20 [PATCH v4 0/4] tools: Add a toplevel Makefile Borislav Petkov
2012-04-10 15:20 ` [PATCH v4 1/4] tools: Add Makefile.include Borislav Petkov
2012-04-10 20:27 ` Sam Ravnborg
2012-04-10 20:58 ` Borislav Petkov
2012-04-10 15:20 ` [PATCH v4 2/4] tools: Add a toplevel Makefile Borislav Petkov
2012-04-10 20:33 ` Sam Ravnborg
2012-04-10 21:03 ` Borislav Petkov
2012-04-10 15:20 ` [PATCH v4 3/4] tools: Add a help target Borislav Petkov
2012-04-10 20:34 ` Sam Ravnborg
2012-04-10 15:20 ` [PATCH v4 4/4] tools: Connect to the kernel build system Borislav Petkov
2012-04-10 20:37 ` Sam Ravnborg
2012-04-10 21:04 ` Borislav Petkov [this message]
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=20120410210457.GD30366@aftab \
--to=bp@amd64.org \
--cc=acme@infradead.org \
--cc=borislav.petkov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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 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.