From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jens Freimann <jfreimann@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw36172 [PATCH 17/17] vhost: support mergeable rx buffers with packed queues
Date: Fri, 16 Mar 2018 16:23:30 +0100 (CET) [thread overview]
Message-ID: <20180316152330.C016BAAA4@dpdk.org> (raw)
In-Reply-To: <20180316152120.13199-18-jfreimann@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/36172
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#17:
packed virtqueues. The difference to split virtqueues is not big, it differs
ERROR:SPACING: spaces required around that '=' (ctx:VxW)
#56: FILE: lib/librte_vhost/virtio_net.c:409:
+ struct vring_desc_packed *descs= vq->desc_packed;
^
WARNING:BRACES: braces {} are not necessary for any arm of this statement
#144: FILE: lib/librte_vhost/virtio_net.c:493:
+ if (dev->features & (1ULL << VIRTIO_F_RING_PACKED)) {
[...]
+ } else {
[...]
ERROR:SPACING: need consistent spacing around '-' (ctx:WxV)
#145: FILE: lib/librte_vhost/virtio_net.c:494:
+ idx = vq->last_avail_idx & (vq->size -1);
^
total: 2 errors, 2 warnings, 276 lines checked
parent reply other threads:[~2018-03-16 15:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180316152120.13199-18-jfreimann@redhat.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=20180316152330.C016BAAA4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jfreimann@redhat.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).