From: "André Almeida" <andrealmeid@collabora.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Darren Hart <dvhart@infradead.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>
Subject: Re: [PATCH] selftests: futex: Use variable MAKE instead of make
Date: Thu, 27 Jan 2022 15:09:44 -0300 [thread overview]
Message-ID: <65054310-e925-4072-7df2-e1550d8a9a4f@collabora.com> (raw)
In-Reply-To: <20220127174447.754605-1-usama.anjum@collabora.com>
Hi Usama,
Às 14:44 de 27/01/22, Muhammad Usama Anjum escreveu:
> Recursive make commands should always use the variable MAKE, not the
> explicit command name ‘make’. This has benefits and removes the
> following warning when multiple jobs are used for the build:
>
> make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
>
> Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
Thanks for the patch!
Reviewed-by: André Almeida <andrealmeid@collabora.com>
> ---
> tools/testing/selftests/futex/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/futex/Makefile b/tools/testing/selftests/futex/Makefile
> index 12631f0076a10..11e157d7533b8 100644
> --- a/tools/testing/selftests/futex/Makefile
> +++ b/tools/testing/selftests/futex/Makefile
> @@ -11,7 +11,7 @@ all:
> @for DIR in $(SUBDIRS); do \
> BUILD_TARGET=$(OUTPUT)/$$DIR; \
> mkdir $$BUILD_TARGET -p; \
> - make OUTPUT=$$BUILD_TARGET -C $$DIR $@;\
> + $(MAKE) OUTPUT=$$BUILD_TARGET -C $$DIR $@;\
> if [ -e $$DIR/$(TEST_PROGS) ]; then \
> rsync -a $$DIR/$(TEST_PROGS) $$BUILD_TARGET/; \
> fi \
> @@ -32,6 +32,6 @@ override define CLEAN
> @for DIR in $(SUBDIRS); do \
> BUILD_TARGET=$(OUTPUT)/$$DIR; \
> mkdir $$BUILD_TARGET -p; \
> - make OUTPUT=$$BUILD_TARGET -C $$DIR $@;\
> + $(MAKE) OUTPUT=$$BUILD_TARGET -C $$DIR $@;\
> done
> endef
next prev parent reply other threads:[~2022-01-27 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 17:44 Muhammad Usama Anjum
2022-01-27 18:09 ` André Almeida [this message]
2022-01-27 22:52 ` Shuah Khan
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=65054310-e925-4072-7df2-e1550d8a9a4f@collabora.com \
--to=andrealmeid@collabora.com \
--cc=bamvor.zhangjian@linaro.org \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=usama.anjum@collabora.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
Powered by JetHome