From: Anton Eliasson <anton.eliasson@axis.com>
To: Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>
Cc: <cocci@inria.fr>, <linux-kernel@vger.kernel.org>,
Anton Eliasson <anton.eliasson@axis.com>, <kernel@axis.com>
Subject: [PATCH 1/2] scripts: coccicheck: Return error from run_cmd_parmap
Date: Tue, 3 Oct 2023 16:25:14 +0200 [thread overview]
Message-ID: <20231003-coccicheck-v1-1-07d2d900a52a@axis.com> (raw)
In-Reply-To: <20231003-coccicheck-v1-0-07d2d900a52a@axis.com>
Exiting on error breaks the chain mode. Return the error instead in
order for the caller to propagate it or in the case of chain, try the
next mode.
Signed-off-by: Anton Eliasson <anton.eliasson@axis.com>
---
scripts/coccicheck | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/coccicheck b/scripts/coccicheck
index e52cb43fede6..95a312730e98 100755
--- a/scripts/coccicheck
+++ b/scripts/coccicheck
@@ -153,7 +153,7 @@ run_cmd_parmap() {
err=$?
if [[ $err -ne 0 ]]; then
echo "coccicheck failed"
- exit $err
+ return $err
fi
}
--
2.30.2
next prev parent reply other threads:[~2023-10-03 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 14:25 [PATCH 0/2] coccicheck bugfix and CI improvement Anton Eliasson
2023-10-03 14:25 ` Anton Eliasson [this message]
2023-11-02 21:27 ` [cocci] [PATCH 1/2] scripts: coccicheck: Return error from run_cmd_parmap Julia Lawall
2023-11-17 16:36 ` Anton Eliasson
2023-10-03 14:25 ` [PATCH 2/2] scripts: coccicheck: Separate spatch stdout and stderr Anton Eliasson
2023-10-07 19:41 ` [cocci] " Julia Lawall
2023-10-10 15:59 ` Anton Eliasson
2023-10-10 16:11 ` Julia Lawall
2023-10-11 13:19 ` Anton Eliasson
2023-10-11 13:46 ` Julia Lawall
2023-10-11 13:57 ` Anton Eliasson
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=20231003-coccicheck-v1-1-07d2d900a52a@axis.com \
--to=anton.eliasson@axis.com \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
/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