From: Borislav Petkov <email@example.com> To: Ingo Molnar <firstname.lastname@example.org>, Arnaldo Carvalho de Melo <email@example.com>, Michal Marek <firstname.lastname@example.org>, Sam Ravnborg <email@example.com> Cc: LKML <firstname.lastname@example.org>, Borislav Petkov <email@example.com> Subject: [PATCH v5 0/5] tools: Add a toplevel Makefile Date: Wed, 11 Apr 2012 18:36:13 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) From: Borislav Petkov <email@example.com> Hi all, this is v5 of the patchset incorporating most of Sam's comments from yesterday. Changelog: ========== * v4: this is basically a new rediff of the patchset against 3.4-rc2 along with integrating all comments/reviews I got from the last iteration. If there are none this time, I would like to suggest merging this, maybe through -tip or Arnaldo's perf tree. State of the affairs on how to use it are in the 4/4 patch, adding them here too: 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. Thanks. * v3: Yet another version of the toplevel Makefile integration of tools/. This round gives you the ability to build the tools from the toplevel Makefile (explanation below can be found also in patch 4/4's commit message): "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> tinstall The install target is called "tinstall" so that there's no conflict with the main kernel install target and should mean "tool install". $ make tools/ <toolname>_clean should clean the respective tool directories. If you want to clean all in tools, simply do $ make tools/ cleanall Also, if you want to get what the possible targets are, simply calling $ make tools/ should give you the short help." Also included are all suggestions from the last time. Thanks. * v2: 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 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 Cleaning targets: all of the above with the "_clean" string appended cleans the respective build directory. clean: a summary clean target to clean _all_ folders * v1: 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. </Changelog> Any comments/suggestions are welcome, thanks.
next reply other threads:[~2012-04-11 16:37 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-11 16:36 Borislav Petkov [this message] 2012-04-11 16:36 ` [PATCH v5 1/5] tools: Add Makefile.include Borislav Petkov 2012-04-13 18:14 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 2/5] tools: Cleanup EXTRA_WARNINGS Borislav Petkov 2012-04-13 18:15 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 3/5] tools: Add a toplevel Makefile Borislav Petkov 2012-04-13 18:16 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 4/5] tools: Add a help target Borislav Petkov 2012-04-13 18:17 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 5/5] tools: Connect to the kernel build system Borislav Petkov 2012-04-11 18:04 ` Arnaldo Carvalho de Melo 2012-04-11 18:08 ` Arnaldo Carvalho de Melo 2012-04-11 18:19 ` David Ahern 2012-04-11 19:45 ` Borislav Petkov 2012-04-11 19:52 ` Arnaldo Carvalho de Melo 2012-04-12 15:22 ` Borislav Petkov 2012-04-12 15:57 ` Sam Ravnborg 2012-04-12 18:33 ` Arnaldo Carvalho de Melo 2012-04-12 19:16 ` Sam Ravnborg 2012-04-12 19:31 ` Arnaldo Carvalho de Melo 2012-04-12 21:17 ` Alex Riesen 2012-04-13 10:45 ` Borislav Petkov 2012-04-11 19:47 ` Borislav Petkov 2012-04-13 18:18 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-14 6:35 ` Alex Riesen
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v5 0/5] tools: Add a toplevel Makefile' \ /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
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.