From: "Daniel Díaz" <daniel.diaz@linaro.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: shuahkh@osg.samsung.com, linux-kselftest@vger.kernel.org,
Fathi Boudra <fathi.boudra@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Shuah Khan <shuah@kernel.org>,
"open list:GPIO MOCKUP DRIVER" <linux-gpio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] selftests: gpio: restructure Makefile
Date: Wed, 21 Feb 2018 16:45:17 -0600 [thread overview]
Message-ID: <290910ca-2e0f-8550-0f9c-e48cf277a27c@linaro.org> (raw)
In-Reply-To: <CAHp75VdceMCPw1b8NNoNLTqU-7b7gZ6b8i6eS1MF8eUTH7Lcjg@mail.gmail.com>
Hello!
On 02/21/2018 04:06 PM, Andy Shevchenko wrote:
> On Wed, Feb 21, 2018 at 11:52 PM, Daniel Díaz <daniel.diaz@linaro.org> wrote:
>> From: Fathi Boudra <fathi.boudra@linaro.org>
>
> What are you doing here?
> Why?
> What is the benefit of it?
Thanks for looking into this. I will resend with description.
The purpose of the patch is to clean up the Makefile by restructuring
explicit paths in targets for variables, substituting a variable
(BINARIES) for one of the build system (TEST_PROGS_EXTENDED), and proper
cleaning up of the EXTRA objects.
The resulting Makefile is much more readable and manageable.
Greetings!
Daniel Díaz
daniel.diaz@linaro.org
next prev parent reply other threads:[~2018-02-21 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 21:52 Daniel Díaz
2018-02-21 21:52 ` [PATCH 2/2] selftests/gpio: Fix OUTPUT directory in Makefile Daniel Díaz
2018-02-21 22:09 ` Andy Shevchenko
2018-02-21 23:04 ` Daniel Díaz
2018-02-21 23:11 ` Shuah Khan
2018-02-21 22:06 ` [PATCH 1/2] selftests: gpio: restructure Makefile Andy Shevchenko
2018-02-21 22:45 ` Daniel Díaz [this message]
2018-02-21 23:22 ` [PATCH v2] " Daniel Díaz
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=290910ca-2e0f-8550-0f9c-e48cf277a27c@linaro.org \
--to=daniel.diaz@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=fathi.boudra@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
/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®