From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jens Freimann <jfreimann@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw37282 [PATCH v3 21/21] vhost: add event suppression for packed queues
Date: Thu, 5 Apr 2018 12:13:21 +0200 (CEST) [thread overview]
Message-ID: <20180405101321.EA4401CAE0@dpdk.org> (raw)
In-Reply-To: <20180405101031.26468-22-jfreimann@redhat.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/37282
_coding style issues_
ERROR:CODE_INDENT: code indent should use tabs where possible
#76: FILE: lib/librte_vhost/vhost.h:79:
+ uint16_t desc_event_off_wrap;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#76: FILE: lib/librte_vhost/vhost.h:79:
+ uint16_t desc_event_off_wrap;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#77: FILE: lib/librte_vhost/vhost.h:80:
+ uint16_t desc_event_flags;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#77: FILE: lib/librte_vhost/vhost.h:80:
+ uint16_t desc_event_flags;$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 24)
#165: FILE: lib/librte_vhost/vhost.h:493:
+ if (do_kick)
+ eventfd_write(vq->callfd, (eventfd_t)1);
WARNING:LONG_LINE: line over 90 characters
#186: FILE: lib/librte_vhost/vhost_user.c:480:
+ vq->driver_event = (struct vring_packed_desc_event *)(uintptr_t)ring_addr_to_vva(dev,
WARNING:LONG_LINE: line over 90 characters
#187: FILE: lib/librte_vhost/vhost_user.c:481:
+ vq, addr->avail_user_addr, sizeof(struct vring_packed_desc_event));
WARNING:LONG_LINE: line over 90 characters
#195: FILE: lib/librte_vhost/vhost_user.c:489:
+ vq->device_event = (struct vring_packed_desc_event *)(uintptr_t)ring_addr_to_vva(dev,
WARNING:LONG_LINE: line over 90 characters
#196: FILE: lib/librte_vhost/vhost_user.c:490:
+ vq, addr->used_user_addr, sizeof(struct vring_packed_desc_event));
total: 2 errors, 7 warnings, 171 lines checked
parent reply other threads:[~2018-04-05 10:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180405101031.26468-22-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=20180405101321.EA4401CAE0@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).