From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>
Subject: |WARNING| pw143775 [PATCH 01/11] devtools: fix forbidden token check with multiple files
Date: Sat, 7 Sep 2024 16:55:44 +0200 (CEST) [thread overview]
Message-ID: <20240907145544.040A3121D10@dpdk.org> (raw)
In-Reply-To: <20240907145433.1479091-2-david.marchand@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143775
_coding style issues_
ERROR:DIFF_IN_COMMIT_MSG: Avoid using diff content in the commit message - patch(1) might not work
#80:
--- a/drivers/plop1
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit b467d38284b1 ("devtools: add explicit warnings for forbidden tokens")'
#94:
b467d38284b1 ("devtools: add explicit warnings for forbidden tokens").
total: 2 errors, 0 warnings, 23 lines checked
parent reply other threads:[~2024-09-07 14:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240907145433.1479091-2-david.marchand@redhat.com>]
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=20240907145544.040A3121D10@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=david.marchand@redhat.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).