automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-test-report] |WARNING| pw31658 [PATCH v2 2/3] vhost: protect dirty logging against logging base change
Date: Mon, 27 Nov 2017 12:25:43 +0100 (CET)	[thread overview]
Message-ID: <20171127112543.10DAB1D90@dpdk.org> (raw)
In-Reply-To: <20171124180826.18439-3-maxime.coquelin@redhat.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#26: 
0x00000000004bfc8a in vhost_set_bit (addr=0x7f71cbe18432 <error: Cannot access memory at address 0x7f71cbe18432>, nr=1) at /home/max/projects/src/mainline/dpdk/lib/librte_vhost/vhost.h:267

WARNING:LONG_LINE: line over 90 characters
#85: FILE: lib/librte_vhost/vhost.h:290:
+				(dev->log_size <= ((addr + len - 1) / VHOST_LOG_PAGE / 8))))

total: 0 errors, 2 warnings, 59 lines checked

           reply	other threads:[~2017-11-27 11:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20171124180826.18439-3-maxime.coquelin@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=20171127112543.10DAB1D90@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=maxime.coquelin@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).