From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] cpupower tool: allow building output to be in a separate directory
Date: Mon, 06 Feb 2012 11:45:41 +0100 [thread overview]
Message-ID: <4F2FAF55.9050702@gmail.com> (raw)
In-Reply-To: <20120205203215.GB11621@comet.dominikbrodowski.net>
On 02/05/2012 09:32 PM, Dominik Brodowski wrote:
> Hey,
>
> On Wed, Feb 01, 2012 at 12:08:17PM +0100, Franck Bui-Huu wrote:
>> 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.
>
> Thanks for your patches. I've applied all of them and will push them in the
> next merge window.
>
Thank you Dominik.
--
Franck
prev parent reply other threads:[~2012-02-06 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 11:08 [PATCH 0/3] cpupower tool: allow building output to be in a separate directory Franck Bui-Huu
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 [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=4F2FAF55.9050702@gmail.com \
--to=vagabon.xyz@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 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.