From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jiayu Hu <jiayu.hu@intel.com>
Subject: |WARNING| pw106987 [PATCH v3 1/1] vhost: integrate dmadev in asynchronous data-path
Date: Tue, 8 Feb 2022 03:39:23 +0100 (CET) [thread overview]
Message-ID: <20220208023923.1B40B120715@dpdk.org> (raw)
In-Reply-To: <20220208104031.1885640-2-jiayu.hu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106987
_coding style issues_
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#1373: FILE: lib/vhost/vhost.c:1654:
+ async->pkts_cmpl_flag = rte_zmalloc_socket(NULL, vq->size * sizeof(bool), RTE_CACHE_LINE_SIZE,
WARNING:LONG_LINE: line length of 104 exceeds 100 columns
#1756: FILE: lib/vhost/virtio_net.c:112:
+ ret = vhost_async_dma_transfer_one(dev, vq, dma_id, vchan_id, head_idx, &pkts[pkt_idx]);
WARNING:LONG_LINE: line length of 102 exceeds 100 columns
#1931: FILE: lib/vhost/virtio_net.c:1829:
+ n_xfer = vhost_async_dma_transfer(dev, vq, dma_id, vchan_id, async->pkts_idx, async->iov_iter,
total: 0 errors, 3 warnings, 1610 lines checked
next parent reply other threads:[~2022-02-08 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220208104031.1885640-2-jiayu.hu@intel.com>
2022-02-08 2:39 ` checkpatch [this message]
2022-02-08 2:58 |WARNING| pw106987 [PATCH] [v3, " dpdklab
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=20220208023923.1B40B120715@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jiayu.hu@intel.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).