From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: michal.lkml@markovi.net, linux-kbuild@vger.kernel.org,
yamada.masahiro@socionext.com,
clang-built-linux@googlegroups.com, apw@canonical.com,
joe@perches.com, linux-riscv@lists.infradead.org, info@metux.net
Subject: [PATCH 3/4] scripts: checkpatch.pl: don't complain that debian/rules is executable
Date: Tue, 9 Jul 2019 11:32:38 +0200 [thread overview]
Message-ID: <1562664759-16009-3-git-send-email-info@metux.net> (raw)
In-Reply-To: <1562664759-16009-1-git-send-email-info@metux.net>
checkpatch.pl complains when adding executable "debian/rules",
obviously a false alarm. Therefore add an exception for that.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
scripts/checkpatch.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 342c7c7..caf0146 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2587,6 +2587,7 @@ sub process {
if ($line =~ /^new (file )?mode.*[7531]\d{0,2}$/) {
my $permhere = $here . "FILE: $realfile\n";
if ($realfile !~ m@scripts/@ &&
+ $realfile !~ "debian/rules" &&
$realfile !~ /\.(py|pl|awk|sh)$/) {
ERROR("EXECUTE_PERMISSIONS",
"do not set execute permissions for source files\n" . $permhere);
--
1.9.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-07-09 9:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 9:32 [PATCH 1/4] Makefile: rules for printing kernel architecture and localversion Enrico Weigelt, metux IT consult
2019-07-09 9:32 ` [PATCH 2/4] scripts: mkdebian: allow renaming generated debian/rules via env Enrico Weigelt, metux IT consult
2019-07-09 9:32 ` Enrico Weigelt, metux IT consult [this message]
2019-07-09 10:16 ` [PATCH 3/4] scripts: checkpatch.pl: don't complain that debian/rules is executable Joe Perches
2019-07-09 9:32 ` [PATCH 4/4] debian: add generic rule file Enrico Weigelt, metux IT consult
2019-07-15 12:28 ` Masahiro Yamada
2019-07-15 18:56 ` Enrico Weigelt, metux IT consult
2019-07-15 19:12 ` Theodore Y. Ts'o
2019-07-16 8:58 ` Masahiro Yamada
2019-07-16 12:34 ` Theodore Y. Ts'o
2019-07-17 14:16 ` Enrico Weigelt, metux IT consult
2019-07-17 15:23 ` Theodore Y. Ts'o
2019-07-17 11:08 ` Enrico Weigelt, metux IT consult
2019-07-09 14:54 ` [PATCH 1/4] Makefile: rules for printing kernel architecture and localversion Randy Dunlap
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=1562664759-16009-3-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=apw@canonical.com \
--cc=clang-built-linux@googlegroups.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michal.lkml@markovi.net \
--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).