automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: nickcooper-zhangtonghao <nic@opencloud.tech>
Subject: [dpdk-test-report] |WARNING| pw18906 [PATCH 5/5] vmxnet3: Avoid segfault caused by vmxnet3_dev_tx_queue_setup.
Date: Thu,  5 Jan 2017 11:43:46 +0100 (CET)	[thread overview]
Message-ID: <20170105104346.31E68F923@dpdk.org> (raw)
In-Reply-To: <1483612983-3545-5-git-send-email-nic@opencloud.tech>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'mumber' may be misspelled - perhaps 'number'?
#48: 
We should allocate Tx ring for max possible mumber of hardware descriptors.

WARNING:TYPO_SPELLING: 'mumber' may be misspelled - perhaps 'number'?
#68: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:877:
+    /* Allocate Tx ring for max possible mumber of hardware descriptors. */

CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_TxDesc>
#69: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:878:
+	size = sizeof(struct Vmxnet3_TxDesc) * VMXNET3_TX_RING_MAX_SIZE;

CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_TxCompDesc>
#70: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:879:
+	size += sizeof(struct Vmxnet3_TxCompDesc) * VMXNET3_TX_RING_MAX_SIZE;

CHECK:CAMELCASE: Avoid CamelCase: <Vmxnet3_TxDataDesc>
#71: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:880:
+	size += sizeof(struct Vmxnet3_TxDataDesc) * VMXNET3_TX_RING_MAX_SIZE;

total: 0 errors, 2 warnings, 3 checks, 13 lines checked

           reply	other threads:[~2017-01-05 10:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1483612983-3545-5-git-send-email-nic@opencloud.tech>]

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=20170105104346.31E68F923@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=nic@opencloud.tech \
    --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).