From: Franck Bui-Huu <fbuihuu@gmail.com>
To: linux@dominikbrodowski.net
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] cpupower tool: allow building output to be in a separate directory
Date: Wed, 1 Feb 2012 12:08:17 +0100 [thread overview]
Message-ID: <1328094500-19393-1-git-send-email-fbuihuu@gmail.com> (raw)
Hello Dominik,
This small patchset gives to the user the ability to build cpupower
tool even if the source code is stored in a read-only location.
Patches #1 and #2 are just minor cleanup in order to ease patch #3
which adds the functionnality.
Please consider.
Franck Bui-Huu (3):
cpupower tool: remove use of undefined variables from the clean target of the top makefile
cpupower tool: makefile: simplify the recipe used to generate cpupower.pot target
cpupower tool: allow to build in a separate directory
tools/power/cpupower/Makefile | 93 +++++++++++++++++++++-------------
tools/power/cpupower/bench/Makefile | 23 ++++++---
2 files changed, 72 insertions(+), 44 deletions(-)
--
1.7.7.4
next reply other threads:[~2012-02-01 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 11:08 Franck Bui-Huu [this message]
2012-02-01 11:08 ` [PATCH 1/3] cpupower tool: remove use of undefined variables from the clean target of the top makefile Franck Bui-Huu
2012-02-01 11:08 ` [PATCH 2/3] cpupower tool: makefile: simplify the recipe used to generate cpupower.pot target Franck Bui-Huu
2012-02-01 11:08 ` [PATCH 3/3] cpupower tool: allow to build in a separate directory Franck Bui-Huu
2012-02-05 20:32 ` [PATCH 0/3] cpupower tool: allow building output to be " Dominik Brodowski
2012-02-06 10:45 ` Franck Bui-Huu
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=1328094500-19393-1-git-send-email-fbuihuu@gmail.com \
--to=fbuihuu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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;
as well as URLs for NNTP newsgroup(s).