From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Masahiro Yamada <yamada.masahiro@socionext•com>,
linuxppc-dev@lists•ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs•ru>,
linux-kernel@vger•kernel.org, Nicholas Piggin <npiggin@gmail•com>,
Masahiro Yamada <yamada.masahiro@socionext•com>,
Firoz Khan <firoz.khan@linaro•org>, Joel Stanley <joel@jms•id.au>,
Andrew Donnellan <andrew.donnellan@au1•ibm.com>,
Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH] powerpc: improve prom_init_check rule
Date: Thu, 19 Sep 2019 20:26:02 +1000 (AEST) [thread overview]
Message-ID: <46YtKk2RyPz9sPf@ozlabs.org> (raw)
In-Reply-To: <20190912074037.13813-1-yamada.masahiro@socionext.com>
On Thu, 2019-09-12 at 07:40:37 UTC, Masahiro Yamada wrote:
> This slightly improves the prom_init_check rule.
>
> [1] Avoid needless check
>
> Currently, prom_init_check.sh is invoked every time you run 'make'
> even if you have changed nothing in prom_init.c. With this commit,
> the script is re-run only when prom_init.o is recompiled.
>
> [2] Beautify the build log
>
> Currently, the O= build shows the absolute path to the script:
>
> CALL /abs/path/to/source/of/linux/arch/powerpc/kernel/prom_init_check.sh
>
> With this commit, it is always a relative path to the timestamp file:
>
> PROMCHK arch/powerpc/kernel/prom_init_check
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext•com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/1fdfa4c6af0cc1854b017f308af6bece94568bb6
cheers
prev parent reply other threads:[~2019-09-19 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 7:40 [PATCH] powerpc: improve prom_init_check rule Masahiro Yamada
2019-09-19 10:26 ` Michael Ellerman [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=46YtKk2RyPz9sPf@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=aik@ozlabs$(echo .)ru \
--cc=andrew.donnellan@au1$(echo .)ibm.com \
--cc=firoz.khan@linaro$(echo .)org \
--cc=joel@jms$(echo .)id.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=yamada.masahiro@socionext$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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