From: Joe Perches <joe@perches.com>
To: Dirk Gouders <dirk@gouders.net>
Cc: Andy Whitcroft <apw@canonical.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] checkpatch: kbuild: if_changed: check for multiple calls in targets
Date: Fri, 20 Jul 2018 03:06:37 -0700 [thread overview]
Message-ID: <01cfa83d2e29667d311d679c904b1648cd35c614.camel@perches.com> (raw)
In-Reply-To: <20180720074804.4160-1-dirk@gouders.net>
On Fri, 2018-07-20 at 09:48 +0200, Dirk Gouders wrote:
> The kbuild function if_changed should not be called more than once for
> a target.
>
> Because that function writes the command line to a .cmd file for later
> tests, multiple calls of it within a target would result in overwrites
> of previous values and effectively render the command line test
> meaningless, resulting in flip-flop behaviour.
>
> Add a check for makefiles and kbuild files and produce an error for
> targets with multiple calls to if_changed.
>
> Three examples that now could be detected:
>
> 98f78525371b55ccd (x86/boot: Refuse to build with data relocations)
> 6a8dfe1cac5c591ae (microblaze: support U-BOOT image format)
> 684151a75bf25f5ae (sparc32: added U-Boot build target: uImage)
>
> Reviewed-by: Joe Perches <joe@perches.com>
I didn't review this. I gave you feedback
but didn't add a signature.
For anything other than "Suggested-by:",
please don't add signatures to patches unless
the person gives directly gives you one.
> Suggested-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> Signed-off-by: Dirk Gouders <dirk@gouders.net>
> ---
> v2: rework commit message and regular expression
> ---
> scripts/checkpatch.pl | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 447857ffaf6b..437e98414f74 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2911,6 +2911,14 @@ sub process {
> "Use of $flag is deprecated, please use \`$replacement->{$flag} instead.\n" . $herecurr) if ($replacement->{$flag});
> }
>
> + # Check for multiple calls of if_changed within a target in Makefiles
> + if (($realfile =~ /Makefile.*/ || $realfile =~ /Kbuild.*/) &&
The uses of .* here are superfluous.
> + ($prevline =~ /^[ +]\t\s*\$\(call\s+if_changed,/) &&
> + ($line =~ /^[ +]\t\s*\$\(call\s+if_changed,/)) {
> + ERROR("MULTIPLE_IF_CHANGED",
> + "Multiple calls of if_changed within a target.\n" . $herecurr);
> + }
> +
> # check for DT compatible documentation
> if (defined $root &&
> (($realfile =~ /\.dtsi?$/ && $line =~ /^\+\s*compatible\s*=\s*\"/) ||
next prev parent reply other threads:[~2018-07-20 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 12:39 [PATCH] checkpatch: if_changed: check for multiple calls in targets Dirk Gouders
2018-07-16 15:23 ` Joe Perches
2018-07-17 9:32 ` Dirk Gouders
2018-07-20 7:48 ` [PATCH v2] checkpatch: kbuild: " Dirk Gouders
2018-07-20 10:06 ` Joe Perches [this message]
2018-07-20 15:21 ` Segher Boessenkool
2018-07-20 15:33 ` Joe Perches
2018-07-20 15:44 ` Segher Boessenkool
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=01cfa83d2e29667d311d679c904b1648cd35c614.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).