From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-test-report] |WARNING| pw31187 [PATCH v4 07/15] memzone: rename address from physical to IOVA
Date: Mon, 6 Nov 2017 02:43:08 +0100 (CET) [thread overview]
Message-ID: <20171106014308.4AE271B32C@dpdk.org> (raw)
In-Reply-To: <20171106014141.13266-8-thomas@monjalon.net>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/31187
_coding style issues_
CHECK:SPACING: No space is necessary after a cast
#74: FILE: drivers/net/bnx2x/bnx2x.c:187:
+ dma->paddr = (uint64_t) z->iova;
CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#87: FILE: drivers/net/bnx2x/bnx2x_rxtx.c:111:
+ fp->rx_desc_mapping = rxq->rx_ring_phys_addr = (uint64_t)dma->iova;
CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#96: FILE: drivers/net/bnx2x/bnx2x_rxtx.c:157:
+ fp->rx_comp_mapping = rxq->cq_ring_phys_addr = (uint64_t)dma->iova;
CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#105: FILE: drivers/net/bnx2x/bnx2x_rxtx.c:292:
+ fp->tx_desc_mapping = txq->tx_ring_phys_addr = (uint64_t)tz->iova;
CHECK:CAMELCASE: Avoid CamelCase: <sharedPA>
#581: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:487:
+ hw->sharedPA = mz->iova;
CHECK:CAMELCASE: Avoid CamelCase: <queueDescPA>
#590: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:508:
+ hw->queueDescPA = mz->iova;
CHECK:CAMELCASE: Avoid CamelCase: <rss_confPA>
#599: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:524:
+ hw->rss_confPA = mz->iova;
CHECK:CAMELCASE: Avoid CamelCase: <memRegsPA>
#608: FILE: drivers/net/vmxnet3/vmxnet3_ethdev.c:572:
+ hw->memRegsPA = mz->iova;
CHECK:CAMELCASE: Avoid CamelCase: <basePA>
#621: FILE: drivers/net/vmxnet3/vmxnet3_rxtx.c:982:
+ ring->basePA = mz->iova;
WARNING:LONG_LINE: line over 90 characters
#764: FILE: test/test/test_memzone.c:567:
+ memzone_aligned_128->iova, memzone_aligned_128->len))
WARNING:LONG_LINE: line over 90 characters
#769: FILE: test/test/test_memzone.c:570:
+ memzone_aligned_256->iova, memzone_aligned_256->len))
WARNING:LONG_LINE: line over 90 characters
#774: FILE: test/test/test_memzone.c:573:
+ memzone_aligned_512->iova, memzone_aligned_512->len))
WARNING:LONG_LINE: line over 90 characters
#779: FILE: test/test/test_memzone.c:576:
+ memzone_aligned_1024->iova, memzone_aligned_1024->len))
WARNING:LONG_LINE: line over 90 characters
#784: FILE: test/test/test_memzone.c:579:
+ memzone_aligned_256->iova, memzone_aligned_256->len))
WARNING:LONG_LINE: line over 90 characters
#789: FILE: test/test/test_memzone.c:582:
+ memzone_aligned_512->iova, memzone_aligned_512->len))
WARNING:LONG_LINE: line over 90 characters
#794: FILE: test/test/test_memzone.c:585:
+ memzone_aligned_1024->iova, memzone_aligned_1024->len))
WARNING:LONG_LINE: line over 90 characters
#799: FILE: test/test/test_memzone.c:588:
+ memzone_aligned_512->iova, memzone_aligned_512->len))
WARNING:LONG_LINE: line over 90 characters
#804: FILE: test/test/test_memzone.c:591:
+ memzone_aligned_1024->iova, memzone_aligned_1024->len))
WARNING:LONG_LINE: line over 90 characters
#809: FILE: test/test/test_memzone.c:594:
+ memzone_aligned_1024->iova, memzone_aligned_1024->len))
total: 0 errors, 10 warnings, 647 lines checked
parent reply other threads:[~2017-11-06 1:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20171106014141.13266-8-thomas@monjalon.net>]
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=20171106014308.4AE271B32C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).