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 2/2] scripts: coccicheck: Separate spatch stdout and stderr
Date: Tue, 3 Oct 2023 16:25:15 +0200 [thread overview]
Message-ID: <20231003-coccicheck-v1-2-07d2d900a52a@axis.com> (raw)
In-Reply-To: <20231003-coccicheck-v1-0-07d2d900a52a@axis.com>
This helps automating coccicheck runs by discarding stderr and only
looking at the output of stdout. In report mode the only remaining
output on stdout is the initial "Please check for false positives"
message followed by each spatch warning found.
Signed-off-by: Anton Eliasson <anton.eliasson@axis.com>
---
scripts/coccicheck | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/coccicheck b/scripts/coccicheck
index 95a312730e98..7e7c44125f47 100755
--- a/scripts/coccicheck
+++ b/scripts/coccicheck
@@ -146,8 +146,8 @@ run_cmd_parmap() {
echo $@>>$DEBUG_FILE
$@ 2>>$DEBUG_FILE
else
- echo $@
- $@ 2>&1
+ echo $@ >&2
+ $@
fi
err=$?
--
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 ` [PATCH 1/2] scripts: coccicheck: Return error from run_cmd_parmap Anton Eliasson
2023-11-02 21:27 ` [cocci] " Julia Lawall
2023-11-17 16:36 ` Anton Eliasson
2023-10-03 14:25 ` Anton Eliasson [this message]
2023-10-07 19:41 ` [cocci] [PATCH 2/2] scripts: coccicheck: Separate spatch stdout and stderr 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-2-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