automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: gavin hu <gavin.hu@arm.com>
Subject: [dpdk-test-report] |WARNING| pw40074 [PATCH] dev Digest Vol 195 Issue 45
Date: Wed, 16 May 2018 04:09:57 +0200 (CEST)	[thread overview]
Message-ID: <20180516020957.070B31B718@dpdk.org> (raw)
In-Reply-To: <DB7PR08MB31637C042CB07826BE425E5F8F920@DB7PR08MB3163.eurprd08.prod.outlook.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/40074

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#31: 
When replying, please edit your Subject line so it is more specific than "Re: Contents of dev digest..."

ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("commit description")'
#95: 
commit 55fbc92d7800100628579643c9ee2770614fef10

WARNING:BAD_SIGN_OFF: Do not use whitespace before Reported-by:
#114: 
    Reported-by: Andrew Rybchenko <arybchenko@solarflare.com>

WARNING:BAD_SIGN_OFF: Do not use whitespace before Signed-off-by:
#115: 
    Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>

WARNING:BAD_SIGN_OFF: Do not use whitespace before Acked-by:
#116: 
    Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

WARNING:BAD_SIGN_OFF: Duplicate signature
#234: 
To: Gavin Hu <gavin.hu@arm.com>

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (0, 0)
#334: FILE: drivers/net/tap/rte_eth_tap.c:506:
+if (txq->type == ETH_TUNTAP_TYPE_TUN) {
[...]
+char *buff_data = rte_pktmbuf_mtod(seg, void *);

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (0, 0)
#378: FILE: drivers/net/tap/rte_eth_tap.c:1433:
+if (pmd->type == ETH_TUNTAP_TYPE_TAP) {
 if (is_zero_ether_addr(mac_addr))

WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (0, 0)
#387: FILE: drivers/net/tap/rte_eth_tap.c:1452:
+if (pmd->type == ETH_TUNTAP_TYPE_TAP) {
 memset(&ifr, 0, sizeof(struct ifreq));

total: 1 errors, 8 warnings, 0 checks, 130 lines checked

           reply	other threads:[~2018-05-16  2:09 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DB7PR08MB31637C042CB07826BE425E5F8F920@DB7PR08MB3163.eurprd08.prod.outlook.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=20180516020957.070B31B718@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=gavin.hu@arm.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).