From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw63215 [PATCH v2 2/3] doc: update release notes for Broadcom PMD
Date: Fri, 22 Nov 2019 00:36:11 +0100 (CET) [thread overview]
Message-ID: <20191121233611.E9F992BBD@dpdk.org> (raw)
In-Reply-To: <20191121233435.4263-2-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/63215
_coding style issues_
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#64:
1) b150a7e7ee66 ("net/bnxt: support LRO on Thor adapters")
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#65:
2) be14720def9c ("net/bnxt: support FW reset")
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#66:
3) df6cd7c1f73a ("net/bnxt: handle reset notify async event from FW")
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#67:
4) 698aa7e95325 ("net/bnxt: add code to determine the Tx COS queue")
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#68:
5) 04102f2ffc8c ("net/bnxt: update HWRM API to version 1.10.1.6")
total: 5 errors, 0 warnings, 16 lines checked
parent reply other threads:[~2019-11-21 23:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20191121233435.4263-2-ajit.khaparde@broadcom.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=20191121233611.E9F992BBD@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ajit.khaparde@broadcom.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).