From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ali Alnubani <alialnu@nvidia.com>
Subject: |WARNING| pw119043 [PATCH] devtools: check for supported git version
Date: Mon, 24 Oct 2022 17:38:43 +0200 (CEST) [thread overview]
Message-ID: <20221024153843.2F52D120778@dpdk.org> (raw)
In-Reply-To: <20221024153706.3117107-1-alialnu@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/119043
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#128:
[1] https://github.com/git/git/blob/v2.19.0/Documentation/RelNotes/2.19.0.txt
WARNING:EMBEDDED_FILENAME: It's generally not useful to have the filename in the file
#145: FILE: devtools/parse-flow-support.sh:17:
+if ! git grep -qo git -- devtools/parse-flow-support.sh >/dev/null 2>&1; then
total: 0 errors, 2 warnings, 12 lines checked
next parent reply other threads:[~2022-10-24 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221024153706.3117107-1-alialnu@nvidia.com>
2022-10-24 15:38 ` checkpatch [this message]
2022-10-24 17:19 ` |SUCCESS| " 0-day Robot
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=20221024153843.2F52D120778@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=alialnu@nvidia.com \
--cc=test-report@dpdk.org \
/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).